Grafana alerts investigated as they fire
Grafana Cloud
Teams on Grafana Cloud or self-hosted Grafana can connect a stack so every alert rule reaches Polylane, which opens an issue and investigates it.
What changed
Connect Grafana Cloud, or self-hosted
Grafana, with a stack URL and a service account token. Polylane adds a contact point and a catch-all notification route to the stack, so every existing alert rule, and every rule you create later, reaches it with no per-rule setup. The route lets every alert continue, so your own alert delivery stays as it is. If the contact point or route is removed, Polylane puts it back within the hour.
When an alert fires, Polylane opens an issue and investigates it, and further notices of the same alert join that issue. Every panel query on your dashboards also becomes a check that runs on a schedule. Investigations can search dashboards, list datasources, read alert rules and annotations, and run queries through your datasources. See the Grafana integration.
Why it matters
Most Grafana setups already have the alert rules a team cares about. Routing all of them to Polylane in one step means every rule is covered from the moment you connect, including rules added next month, and nobody has to remember to subscribe a new one.
How to use it
- Find your stack URL in the
Grafana Cloud portal, under your stack's details.
- In
Grafana, open Administration > Users and access > Service accounts and create a service account with the Editor role. Add the Alerting provisioning writer role to it.
- Add a token to the service account, then paste the stack URL and the token into Polylane under Settings > Integrations.
- If Terraform manages your notification policy tree, add a first route to the
polylanecontact point withcontinue = true, so an apply does not remove it.