Grafana

Connect Grafana so its alerts drive your workflows. When an alert fires (or later resolves), Grafana notifies metamorphOS and a process starts automatically, for example an incident-response workflow.

What you can do

• Alert events: trigger a process automatically when a Grafana alert fires.
• Resolution events: Grafana also notifies metamorphOS when an alert clears, so a process can close the incident it opened.
• Route by alert: send different alerts to different processes using Grafana’s own notification rules.

Every alert arrives with its full detail (severity, labels, summary, runbook link, and links back to the rule and dashboard), so your process can decide what to do.

Before you start

You need a Grafana account with permission to manage Alerting, so you can create a contact point and a notification policy (an admin or editor role).

Connect in metamorphOS

Activate the Grafana connector from the marketplace and add an account. metamorphOS gives you two things to configure Grafana with:

• An inbound webhook URL: the address Grafana will send alerts to. Copy it from the connector.
• A webhook signing secret: choose a long, random value and set it on the account. Grafana presents this secret with every alert, and metamorphOS rejects any delivery that does not match it.

Set up Grafana

1. Create a contact point. In Grafana, go to Alerting → Contact points → Add contact point and choose the Webhook integration.
2. Point it at metamorphOS. Set the URL to the inbound webhook URL from the previous step and leave the method as POST.
3. Add the secret. Under Authentication, choose Bearer and enter the webhook signing secret you set on the account. Leave the default JSON body.
4. Test it. Use Test to send a sample alert; a process should start in metamorphOS.
5. Route your alerts. In Alerting → Notification policies, add a policy that matches the alerts you want (for example severity = critical, or a specific alert name) and set its contact point to the one you just created. This is where you decide which alerts trigger which process: use one contact point per process. You can keep an existing contact point (such as Slack) on the same policy if you also want people notified.

Good to know

• Grafana sends a separate notification when an alert resolves. Each alert carries a stable fingerprint, so a process can match a resolution back to the alert that opened the incident and close it automatically.
• A contact point sends whichever alerts its notification policy matches, so shape what reaches each process in Grafana’s notification rules rather than in the process itself.