mirror of
https://github.com/grafana/grafana.git
synced 2025-09-26 00:43:48 +08:00
596b4fecb0
* Refactors notifications in alerting * Fixes broken links * adds headings * fixes broken links * Adds line space and intro sentences
28 lines
1.4 KiB
Markdown
28 lines
1.4 KiB
Markdown
---
|
|
aliases:
|
|
- /docs/grafana/latest/alerting/alerting-rules/alert-annotation-label/
|
|
- /docs/grafana/latest/alerting/fundamentals/annotation-label/
|
|
- /docs/grafana/latest/alerting/unified-alerting/alerting-rules/alert-annotation-label/
|
|
description: Annotations and labels for alerting
|
|
keywords:
|
|
- grafana
|
|
- alerting
|
|
- guide
|
|
- rules
|
|
- create
|
|
title: Annotations and labels for alerting rules
|
|
weight: 401
|
|
---
|
|
|
|
# Annotations and labels for alerting rules
|
|
|
|
Annotations and labels are key value pairs associated with alerts originating from the alerting rule, datasource response, and as a result of alerting rule evaluation. They can be used in alert notifications directly or in templates and template functions to create notification content dynamically.
|
|
|
|
## Annotations
|
|
|
|
Annotations are key-value pairs that provide additional meta-information about an alert. You can use the following annotations: `description`, `summary`, `runbook_url`, `alertId`, `dashboardUid`, and `panelId`. For example, a description, a summary, and a runbook URL. These are displayed in rule and alert details in the UI and can be used in contact point message templates.
|
|
|
|
## Labels
|
|
|
|
Labels are key-value pairs that contain information about, and are used to uniquely identify an alert. The label set for an alert is generated and added to throughout the alerting evaluation and notification process.
|