From 1797192f0299fd36f04f543dc13ba42c081ca2b4 Mon Sep 17 00:00:00 2001 From: Peter Wu Date: Wed, 18 Nov 2020 20:29:01 +0100 Subject: [PATCH] Fix the alerting rules name description (#7083) (#8197) commit 9875afc491983cc7462fef336ab1c6b67da45020 changed the type from metric names to label values, we might as well adjust the description. The alternative is to revert that commit and restrict names of alerting rules again even if that was not really enforced. Signed-off-by: Peter Wu --- docs/configuration/recording_rules.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/configuration/recording_rules.md b/docs/configuration/recording_rules.md index 4e4fad6d02..94627b629e 100644 --- a/docs/configuration/recording_rules.md +++ b/docs/configuration/recording_rules.md @@ -45,8 +45,10 @@ dashboards, which need to query the same expression repeatedly every time they refresh. Recording and alerting rules exist in a rule group. Rules within a group are -run sequentially at a regular interval. The names of recording and alerting rules +run sequentially at a regular interval. The names of recording rules must be [valid metric names](https://prometheus.io/docs/concepts/data_model/#metric-names-and-labels). +The names of alerting rules must be +[valid label values](https://prometheus.io/docs/concepts/data_model/#metric-names-and-labels). The syntax of a rule file is: