mirror of
https://github.com/grafana/grafana.git
synced 2025-02-14 01:23:32 -06:00
Docs: Fix image paths (#35334)
This commit is contained in:
Sofia Papagiannaki
GitHub
parent
26027fea2a
commit
6a39fc9ae1
@ -29,19 +29,19 @@ This section describes the fields you fill out to create an alert.
|
||||
- **Namespace -** Select an existing rule namespace or click **Add new** to create a new one.
|
||||
- **Group -** Select an existing group within the selected namespace or click **Add new** to create a new one. Newly created rules will be added to the end of the rule group.
|
||||
|
||||
|
||||
|
||||
|
||||
### Query
|
||||
|
||||
Enter a PromQL or LogQL expression. Rule will fire if evaluation result has at least one series with value > 0. An alert will be created per each such series.
|
||||
|
||||
|
||||
|
||||
|
||||
### Conditions
|
||||
|
||||
- **For -** For how long the selected condition should violated before an alert enters `Firing` state. When condition threshold is violated for the first time, an alert becomes `Pending`. If the **for** time elapses and the condition is still violated, it becomes `Firing`. Else it reverts back to `Normal`.
|
||||
|
||||
|
||||
|
||||
|
||||
### Details
|
||||
|
||||
@ -55,7 +55,7 @@ Annotations are key and value pairs that provide additional meta information abo
|
||||
|
||||
Labels are key value pairs that categorize or identify an alert. Labels are used to match alerts in silences or match and groups alerts in notification policies. Labels are also shown in rule or alert details in the UI and can be used in contact type message templates. For example, it is common to add a `severity` label and then configure a separate notification policy for each severity. Or one could add a `team` label and configure team specific notification policies, or silence all alerts for a particular team.
|
||||
|
||||
|
||||
|
||||
|
||||
## Preview alerts
|
||||
|
||||
|
||||
@ -27,7 +27,7 @@ This section describes the fields you fill out to create an alert.
|
||||
- **Alert type -** Select **Grafana managed alert**.
|
||||
- **Folder -** Select a folder this alert rule will belong to. To create a new folder, click on the drop down and type in a new folder name.
|
||||
|
||||
|
||||
|
||||
|
||||
### Query
|
||||
|
||||
@ -51,7 +51,7 @@ If a query returns multiple series, then the aggregation function and threshold
|
||||
|
||||
So, as you can see from the above scenario Grafana will not send out notifications when other series cause the alert to fire if the rule already is in state `Firing`. If you want to have alert per series, create a multi dimensional alert rule as described in the section below.
|
||||
|
||||
|
||||
|
||||
|
||||
#### Multi dimensional rule
|
||||
|
||||
@ -63,7 +63,7 @@ You can use reduce and math expressions to create a rule that will create an ale
|
||||
|
||||
See or [expressions documentation]({{< relref "../../../panels/expressions.md" >}}) for in depth explanation of `math` and `reduce` expressions.
|
||||
|
||||
|
||||
|
||||
|
||||
### Conditions
|
||||
|
||||
@ -87,7 +87,7 @@ See or [expressions documentation]({{< relref "../../../panels/expressions.md" >
|
||||
| Alerting | Set alert rule state to `Alerting` |
|
||||
| OK | Set alert rule state to `Normal` |
|
||||
|
||||
|
||||
|
||||
|
||||
### Details
|
||||
|
||||
@ -101,7 +101,7 @@ Annotations are key and value pairs that provide additional meta information abo
|
||||
|
||||
Labels are key value pairs that categorize or identify an alert. Labels are used to match alerts in silences or match and groups alerts in notification policies. Labels are also shown in rule or alert details in the UI and can be used in contact type message templates. For example, it is common to add a `severity` label and then configure a separate notification policy for each severity. Or one could add a `team` label and configure team specific notification policies, or silence all alerts for a particular team. Labels can also be templated like annotations, for example `{{ $labels.namespace }}/{{ $labels.job }}` will produce a new rule label that will have the evaluated `namespace` and `job` label value added for every alert this rule produces. The rule labels take precedence over the labels produced by the query/condition.
|
||||
|
||||
|
||||
|
||||
|
||||
## Preview alerts
|
||||
|
||||
|
||||
@ -16,13 +16,13 @@ By default, the group view is shown. You can toggle between group or state views
|
||||
|
||||
Group view shows Grafana alert rules grouped by folder and Loki or Prometheus alert rules grouped by `namespace` + `group`. This is the default rule list view, intended for managing rules. You can expand each group to view a list of rules in this group. Each rule can be further expanded to view its details. Action buttons and any alerts spawned by this rule, and each alert can be further expanded to view its details.
|
||||
|
||||
|
||||
|
||||
|
||||
### State view
|
||||
|
||||
State view shows alert rules grouped by state. Use this view to get an overview of which rules are in what state. Each rule can be expanded to view its details. Action buttons and any alerts spawned by this rule, and each alert can be further expanded to view its details.
|
||||
|
||||
|
||||
|
||||
|
||||
## Filter alert rules
|
||||
You can use the following filters to view only alert rules that match specific criteria:
|
||||
@ -35,7 +35,7 @@ You can use the following filters to view only alert rules that match specific c
|
||||
|
||||
A rule row shows the rule state, health, and summary annotation if the rule has one. You can expand the rule row to display rule labels, all annotations, data sources this rule queries, and a list of alert instances spawned from this rule.
|
||||
|
||||
|
||||
|
||||
|
||||
### Edit or delete rule
|
||||
|
||||
|
||||
@ -18,7 +18,7 @@ For example, you could change the number of decimal places shown in all numeric
|
||||
|
||||
Grafana displays a list of field overrides, if any have been created for this panel.
|
||||
|
||||
|
||||
|
||||
|
||||
## Add a field override
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user