Actions
action #126962
closedUse templating for all provisioned "unified alerts" were the original alerts were part of templated dashboards
Status:
Resolved
Priority:
High
Assignee:
Category:
-
Target version:
Start date:
2023-03-30
Due date:
2023-04-15
% Done:
0%
Estimated time:
Tags:
Description
The alerts that were previously part of the generic and workers dashboards have already been templated as part of #125642. Checkout https://gitlab.suse.de/openqa/salt-states-openqa/-/merge_requests/816/diffs to see how it was done. The same should be done for the alerts that were part of the web UI services dashboard (salt-states-openqa/monitoring/grafana/webui.services.json.template
) and the certificates dashboard (salt-states-openqa/monitoring/grafana/certificates.json.template
).
Acceptance criteria¶
- AC1: Alerts previously¹ defined in
salt-states-openqa/monitoring/grafana/webui.services.json.template
are using templating again (instead of having a distinct YAML files for all those alerts). - AC2: Alerts previously¹ defined in
salt-states-openqa/monitoring/grafana/certificates.json.template
are using templating again (instead of having a distinct YAML files for all those alerts). - AC3: All templated alerts still have unique
rule_uid
s (as otherwise Grafana would complain). - AC4: There are no duplicates. Versions of alerts under their old
rule_uid
s have been cleaned up. - AC5: References to corresponding dashboards/panels via IDs still work.
¹ The alerts are actually still defined in those files but no longer used. This should supposedly be cleaned up at some point but for now you can still find them and they might be a useful reference for this task.
Actions