Overview
Grafana sends alerts to aciona.me through a webhook contact point. Each item in the payload’salerts[] becomes an alert in aciona.me, and resolved items automatically close the matching incident.
Prerequisites
- Grafana with Grafana Alerting enabled and permission to create contact points.
- A service created in aciona.me and linked to a team with an active schedule.
1. Create the alert source in aciona.me
Under Alert sources, create a source of type Grafana — for exampleGrafana - production.
2. Copy the URL and the token
3. Configure the contact point in Grafana
- Through the UI
- Through provisioning (YAML)
1
Alerting → Contact points → Add contact point
Name:
aciona-me. Integration: Webhook.2
URL
https://ingress.aciona.me/webhooks/<alertSourceId>3
HTTP Method
POST4
Authentication header
Add the
X-Aciona-Token header with the source token. In versions that expose the field as Authorization Header, use X-Aciona-Token as the name and the token as the value.5
Disable resolved message
Leave it off. This is the critical step of the integration.
6
Save and use the contact point
Point the notification policy (or the alert rules) at the
aciona-me contact point.4. Send a test alert
Use Test on the Grafana contact point, or force an alert rule to fire.5. Confirm the incident
Under Incidents, the alert should appear within seconds, with the title from the Grafana alert and the severity translated from theseverity label.
6. Set up automatic resolution
States normalized by aciona.me, item by item:
Correlation uses Grafana’s
fingerprint, with fallbacks based on the rule identifier. That identifier must stay stable between the trigger and the recovery.
Routing to the right service
Add aservice label to your alert rules with the exact service name in aciona.me:
Troubleshooting
The incident opens but never closes
The incident opens but never closes
“Disable resolved message” is on somewhere — contact point or notification policy. Turn it off in both.
401 response in Grafana
401 response in Grafana
The
X-Aciona-Token header is missing or wrong. If the token was rotated, update the contact point.The incident lands on the wrong service
The incident lands on the wrong service
Add a
service label to the alert rule with the exact service name in aciona.me. Without it, routing falls back to other hints in the payload.Several incidents for the same problem
Several incidents for the same problem
The
fingerprint is changing between triggers — usually because the rule’s labels change. Stabilize the labels that make up the alert’s identity.