From c825dbaf2fd4a9e5be9544bc9884880b8965b0b9 Mon Sep 17 00:00:00 2001 From: David Grant Date: Mon, 22 Apr 2024 12:36:40 -0700 Subject: [PATCH] docs: Fix mangled admonition block in alerting/recording rule docs (#12733) --- docs/sources/alert/_index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/sources/alert/_index.md b/docs/sources/alert/_index.md index 2d4b19477a..ead7c325e7 100644 --- a/docs/sources/alert/_index.md +++ b/docs/sources/alert/_index.md @@ -203,8 +203,8 @@ Another great use case is alerting on high cardinality sources. These are things Creating these alerts in LogQL is attractive because these metrics can be extracted at _query time_, meaning we don't suffer the cardinality explosion in our metrics store. {{% admonition type="note" %}} -As an example, we can use LogQL v2 to help Loki to monitor _itself_, alerting us when specific tenants have queries that take longer than 10s to complete! To do so, we'd use the following query: `sum by (org_id) (rate({job="loki-prod/query-frontend"} |= "metrics.go" | logfmt | duration > 10s [1m]) -{{% /admonition %}}`. +As an example, we can use LogQL v2 to help Loki to monitor _itself_, alerting us when specific tenants have queries that take longer than 10s to complete! To do so, we'd use the following query: `sum by (org_id) (rate({job="loki-prod/query-frontend"} |= "metrics.go" | logfmt | duration > 10s [1m])`. +{{% /admonition %}} ## Interacting with the Ruler