HackerTrans
TopNewTrendsCommentsPastAskShowJobs

danlimerick

no profile record

comments

danlimerick
·il y a 4 ans·discuss
I apologize for the disruption we caused you when rolling out Grafana 9. We are working on improving our releases to Grafana Cloud and also on making sure that errors due to breaking changes in a major release won't affect customers in the future. As a Grafana Cloud customer, you shouldn't need to read docs about breaking changes when we upgrade your instance.
danlimerick
·il y a 5 ans·discuss
Internally (in the Grafana team), we call it unified alerting because it is a unified UI for non-Prometheus data sources together with Prometheus alerting (and Loki/Cortex/Grafana Cloud alerting) and allows you to see all your alerts together.

- For Prometheus, can view and search for alerts.

- For Loki and Cortex, can create and edit alert rules. See Alertmanager data source: https://grafana.com/docs/grafana/latest/datasources/alertman...

- For non-Prometheus data sources, uses the Grafana alerting engine but also has an embedded Alertmanager. Can use the same routing, grouping, deduping and silencing features that Alertmanager provides but for data sources like InfluxDB or MySQL.
danlimerick
·il y a 5 ans·discuss
As Kyle says, we are sidestepping the template variables problem by decoupling alerts from dashboards. You can instead link from an alert to a dashboard or panel (or run book) and get a similar experience to the old alerting.

When you get a notification, you have a link to the appropriate dashboard and it is also easy to create an alert from a query in a dashboard. You can see the linked alert rule in the panel edit mode.