3 ms·
Alert templating. Grafana is fussy about configuring alerts on dashboards that have variables. What this means is if you have 30 clusters and want to use a sing
by wernerb 5y ago
Alert templating. Grafana is fussy about configuring alerts on dashboards that have variables.
What this means is if you have 30 clusters and want to use a single dashboard with a drop-down variable seefting your cluster you cannot define alerts on it. It will refuse to do it.
Alerts are also integrated tightly in dashboards. Forces alerts to be saved/backedup/imported as single json blob. We want separate management of alerts so they can be defined as code and not in the dashboard blob of json!
What makes me chagrined is because of the above issues we have to use prometheus alert manager instead while our colleagues absolutely LOVE grafana itself! We can't duplicate alerts tens of tens times. We don't want that management nor do we want to teach our colleagues jsonnet/ksonnet to generate it. We also don't want permission problems.
- mikewave 5y agoThe new Grafana alerts do absolutely nothing to help with this. I'm at the point where I would pay 5 figures a year for something purely to do better alerting inside or alongside Grafana. Clicking alerts together is a nightmare when I have a ton of identical systems I need to configure. Same for dashboards - the limitations of the current mechanism are too severe. I'd build my own templating mechanism for it, but I still want the alerts visible in Grafana itself. Zabbix has the power to do all this but with a UX that is not ideal....
- treffer 5y agoWell, been down the Prometheus/Alertmanager path and it is pretty workable there. You would get all the templating and grouping by labels. Dashboards can showed Prometheus alerts through annotations on the graphs. So you get a visual feedback what was broken when. Firing alerts are also a metric on Prometheus, so you can list those (or do other stuff with it). It's not a UI thing though. More the lower layers to get stuff for Grafana.