Skip to main content
A Grafana webhook contact point sends alert notifications to Squasher. Each alert in a notification opens its own incident, and the same incident resolves when Grafana sends the alert as resolved.

​
What you need

  • Grafana with Grafana Alerting, and permission to edit contact points and notification policies.
  • The Squasher CLI, signed in with write access to the project. See Alert sources.

​
Connect Grafana

1

Create the connector

Save setup.endpoint and setup.secret from the output.
2

Add a webhook contact point

In Grafana, open Alerting, then Contact points, and add a contact point of the type Webhook. Set the URL to setup.endpoint and the HTTP method to POST.
3

Add the secret

In the optional webhook settings, set the authorization header scheme to Bearer and the credentials to setup.secret. Do not put the secret in the URL.
4

Keep resolved messages on

Do not turn on the option that disables resolved messages. Without them, incidents stay open.
5

Route alerts to the contact point

Save the contact point and select it in the notification policy for your alert rules. Test the contact point in Grafana, then let a real alert rule fire and recover.

​
How Squasher reads a notification

Squasher reads each item in alerts on its own. One notification can open, update, and resolve several incidents. Squasher builds the event key from the fingerprint, the status, the time, and the alert content. A repeated notification with the same content is applied once.

​
Limits

  • Add a severity label to your alert rules. Without it, every incident gets the connector’s default severity.
  • An alert without a fingerprint or a status is rejected. The other alerts in the same notification are still applied, and Squasher returns 207.
  • A notification with an empty alerts list is ignored.

​
Next steps

Alert sources

Limits, response codes, and secret rotation.

Route incidents

Send Grafana incidents to the people on call.