mirror of
https://github.com/grafana/grafana.git
synced 2025-08-02 09:32:23 +08:00

* Use relative aliases for all non-current Grafana aliases Prevents non-latest documentation "stealing" the page away from latest and through permanent redirects for latest pages that no longer exist. The redirected pages are indexed by search engines but our robots.txt forbids them crawling the non-latest page. Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Remove aliases from shared pages Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Rewrite all current latest aliases to be next Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Fix typo in latest alias Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Remove all current page aliases find docs/sources -type f -name '*.md' -exec sed -z -i 's#\n *- /docs/grafana/next/[^\n]*\n#\n#' {} \; find docs/sources -type f -name '*.md' -exec sed -Ez -i 's#\n((aliases:\n *-)|aliases:\n)#\n\2#' {} \; Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Prettier Signed-off-by: Jack Baldry <jack.baldry@grafana.com> Signed-off-by: Jack Baldry <jack.baldry@grafana.com>
844 B
844 B
description | keywords | title | weight | |||
---|---|---|---|---|---|---|
Learn how to organize alert rules |
|
Organising alert rules | 104 |
Namespaces and groups
Alerts can be organized using Folders for Grafana-managed rules and namespaces for Mimir or Loki rules and group names.
Namespaces
When creating Grafana-managed rules, the folder can be used to perform access control and grant or deny access to all rules within a specific folder.
Groups
All rules within a group are evaluated at the same interval.
Alert rules and recording rules within a group will always be evaluated sequentially, meaning no rules will be evaluated at the same time and in order of appearance.
Note
If you want rules to be evaluated concurrently and with different intervals, consider storing them in different groups.