public/grafana
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: overhauled annotation docs and moved some of the data source specific annotation docs to the respective data source doc pages, closes #1111

Browse Source
This commit is contained in:
Torkel Ödegaard
2017-04-28 12:51:21 +02:00
parent c46b73538c
commit 4f9f186575
6 changed files with 64 additions and 36 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/sources/features/datasources/prometheus.md
+12
View File
@@ -81,3 +81,15 @@ When the `Include All` option or `Multi-Value` option is enabled, Grafana conver
Which means you have to use `=~` instead of `=` in your Prometheus queries. For example `ALERTS{instance=~$instance}` instead of `ALERTS{instance=$instance}`.
![](/img/docs/v2/prometheus_templating.png)
## Annotations
[Annotations]({{< relref "reference/Annotations.md" >}}) allows you to overlay rich event information on top of graphs. You add annotation
queries via the Dashboard menu / Annotations view.
Prometheus supports two ways to query annotations.
- A regular metric query
- A Prometheus query for pending and firing alerts (for details see [Inspecting alerts during runtime](https://prometheus.io/docs/alerting/rules/#inspecting-alerts-during-runtime))
The step option is useful to limit the number of events returned from your query.