pez-infra/ansible/services/grafana/provisioning/alerting
Rasmus Wejlgaard c1580a06e2 fix grafana alert rules missing relativeTimeRange
Grafana 12 requires explicit relativeTimeRange on all alert rule data
queries. Without it, queries default to {from: 0, to: 0} which is
rejected as invalid, causing Grafana to crash on startup during
alerting provisioning.

Added relativeTimeRange to all data entries:
- Prometheus queries: {from: 600, to: 0} (10 min lookback)
- Expression refs: {from: 0, to: 0}

This was preventing Grafana from starting on london-a, which meant
alerts (including Host Down for copenhagen-a) could never auto-resolve.
2026-04-04 08:54:58 +00:00
..
contact-points.yml fix remaining yaml lint nitpicks 2026-03-28 13:13:37 +00:00
notification-policy.yml fix last 3 yaml lint failures 2026-03-28 13:17:42 +00:00
rules-critical.yml fix grafana alert rules missing relativeTimeRange 2026-04-04 08:54:58 +00:00
rules-warning.yml fix grafana alert rules missing relativeTimeRange 2026-04-04 08:54:58 +00:00