fix,title
This commit is contained in:
@@ -125,7 +125,7 @@ It should return two series.`desktop` in Firing state, and `mobile` in Normal st
|
||||
|
||||
### Set evaluation behavior
|
||||
|
||||
In the [life cycle](https://grafana.com/docs/grafana/next/alerting/fundamentals/alert-rule-evaluation/) of alert instances, when an alert condition (threshold) is not met, the alert instance state is **Normal**. Similarly, when the condition is breached (for longer than the pending period, which in this tutorial will be 0), the alert instance state switches back to **Alerting**, which means that the alert rule state is **Firing**, and a notification is sent.
|
||||
In the [life cycle](http://grafana.com/docs/grafana/next/alerting/fundamentals/alert-rule-evaluation/) of alert instances, when an alert condition (threshold) is not met, the alert instance state is **Normal**. Similarly, when the condition is breached (for longer than the pending period, which in this tutorial will be 0), the alert instance state switches back to **Alerting**, which means that the alert rule state is **Firing**, and a notification is sent.
|
||||
|
||||
To set up evaluation behavior:
|
||||
|
||||
@@ -141,13 +141,13 @@ In this section, you can select how you want to route your alert instances. Sinc
|
||||
1. Choose **Use notification policy**.
|
||||
1. Click **Preview routing**. Based on the existing labels, you should see a preview of what policies are matching with the alerts. There should be two alert instances matching the labels that were previously setup in each notification policy: `device=desktop`, `device=mobile`.
|
||||
|
||||
These [types of labels](https://grafana.com/docs/grafana/next/alerting/fundamentals/alert-rules/annotation-label/#label-types) are generated by the data source query and they can be leveraged to match our notification policies without needing to manually add them to the alert rule.
|
||||
These [types of labels](https://grafana.com/docs/grafana/latest/alerting/fundamentals/alert-rules/annotation-label/#label-types) are generated by the data source query and they can be leveraged to match our notification policies without needing to manually add them to the alert rule.
|
||||
|
||||
{{< figure src="/media/docs/alerting/get-started-alert-instace-routing-prev.png" max-width="1200px" caption="Routing preview of matched notification policies" >}}
|
||||
{{< figure src="/media/docs/alerting/get-started-alert-instace-routing-prev.png" max-width="1200px" caption="Routing preview of matched notification policies" >}}
|
||||
|
||||
{{< admonition type="note" >}}
|
||||
Even if both labels match the policies, only the alert instance in Firing state produces an alert notification.
|
||||
{{</ admonition >}}
|
||||
{{< admonition type="note" >}}
|
||||
Even if both labels match the policies, only the alert instance in Firing state produces an alert notification.
|
||||
{{</ admonition >}}
|
||||
|
||||
1. Click **Save rule and exit**.
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ Feedback Link: https://github.com/grafana/tutorials/issues/new
|
||||
categories:
|
||||
- alerting
|
||||
description: Get started with Grafana Alerting by creating your first alert in just a few minutes. Learn how to set up an alert, send alert notifications to a public webhook, and generate sample data to observe your alert in action.
|
||||
id: alerting-get-started
|
||||
id: alerting-get-started-pt1
|
||||
labels:
|
||||
products:
|
||||
- enterprise
|
||||
@@ -11,11 +11,11 @@ labels:
|
||||
- cloud
|
||||
tags:
|
||||
- beginner
|
||||
title: Get started with Grafana Alerting
|
||||
title: Get started with Grafana Alerting - Part 1
|
||||
weight: 50
|
||||
---
|
||||
|
||||
# Get Started with Grafana Alerting
|
||||
# Get Started with Grafana Alerting - Part 1
|
||||
|
||||
In this guide, we'll walk you through the process of setting up your first alert in just a few minutes. You'll witness your alert in action with real-time data, as well as sending alert notifications.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user