@@ -38,7 +38,7 @@ This section describes the fields you fill out to create an alert.
### Rule
-**Name -** Enter a descriptive name. The name will be displayed in the Alert Rules list.
-**Evaluate every -** Specify how often the scheduler should evaluate the alert rule. This is referred to as the _evaluation interval_.
-**Evaluate every -**Specify how often the scheduler should evaluate the alert rule. This is referred to as the _evaluation interval_.
-**For -** Specify how long the query needs to violate the configured thresholds before the alert notification triggers.
You can set a minimum evaluation interval in the `alerting.min_interval_seconds` config field, to set a minimum time between evaluations. Refer to [Configuration]({{<relref"../installation/configuration.md">}}#min-interval-seconds) for more information.
...
...
@@ -66,12 +66,12 @@ avg() OF query(A, 15m, now) IS BELOW 14
```
-`avg()` Controls how the values for **each** series should be reduced to a value that can be compared against the threshold. Click on the function to change it to another aggregation function.
-`query(A, 15m, now)`The letter defines what query to execute from the **Metrics** tab. The second two parameters define the time range, `15m, now` means 15 minutes ago to now. You can also do `10m, now-2m` to define a time range that will be 10 minutes ago to 2 minutes ago. This is useful if you want to ignore the last 2 minutes of data.
-`IS BELOW 14` Defines the type of threshold and the threshold value. You can click on `IS BELOW` to change the type of threshold.
-`query(A, 15m, now)` The letter defines what query to execute from the **Metrics** tab. The second two parameters define the time range, `15m, now` means 15 minutes ago to now. You can also do `10m, now-2m` to define a time range that will be 10 minutes ago to 2 minutes ago. This is useful if you want to ignore the last 2 minutes of data.
-`IS BELOW 14`Defines the type of threshold and the threshold value. You can click on `IS BELOW` to change the type of threshold.
The query used in an alert rule cannot contain any template variables. Currently we only support `AND` and `OR` operators between conditions and they are executed serially.
For example, we have 3 conditions in the following order:
*condition:A(evaluates to: TRUE) OR condition:B(evaluates to: FALSE) AND condition:C(evaluates to: TRUE)*
_condition:A(evaluates to: TRUE) OR condition:B(evaluates to: FALSE) AND condition:C(evaluates to: TRUE)_
so the result will be calculated as ((TRUE OR FALSE) AND TRUE) = TRUE.
We plan to add other condition types in the future, like `Other Alert`, where you can include the state of another alert in your conditions, and `Time Of Day`.
...
...
@@ -82,7 +82,7 @@ If a query returns multiple series then the aggregation function and threshold c
- Alert condition with query that returns 2 series: **server1** and **server2**
-**server1** series causes the alert rule to fire and switch to state `Alerting`
- Notifications are sent out with message: _load peaking (server1)_
- Notifications are sent out with message: _load peaking (server1)_
- In a subsequence evaluation of the same alert rule the **server2** series also cause the alert rule to fire
- No new notifications are sent as the alert rule is already in state `Alerting`.
...
...
@@ -95,21 +95,21 @@ So as you can see from the above scenario Grafana will not send out notification
Below are conditions you can configure how the rule evaluation engine should handle queries that return no data or only null values.
No Data Option | Description
------------ | -------------
No Data | Set alert rule state to `NoData`
Alerting | Set alert rule state to `Alerting`
Keep Last State | Keep the current alert rule state, what ever it is.
Ok | Not sure why you would want to send yourself an alert when things are okay, but you could.
| Keep Last State | Keep the current alert rule state, what ever it is. |
If you have an unreliable time series store from which queries sometime timeout or fail randomly you can set this option to `Keep Last State` in order to basically ignore them.
...
...
@@ -121,8 +121,8 @@ The actual notifications are configured and shared between multiple alerts. Read
[Alert notifications]({{<relref"notifications.md">}}) for information on how to configure and set up notifications.
-**Send to -** Select an alert notification channel if you have one set up.
-**Message -** Enter a message to be sent on the notification channel. The message can be in text, markdown, or HTML format. It can include links and variables as well.
-**Tags -**Specify a list of tags (key/value) to be included in the notification. It is only supported by [some notifiers]({{<relref"notifications/#all-supported-notifiers">}}).
-**Message -** Enter a text message to be sent on the notification channel. Some alert notifiers support transforming the text to HTML or other rich formats.
-**Tags -** Specify a list of tags (key/value) to be included in the notification. It is only supported by [some notifiers]({{<relref"notifications/#all-supported-notifiers">}}).
