Skip to main content

Overview

Grafana sends alerts to aciona.me through a webhook contact point. Each item in the payload’s alerts[] 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 example Grafana - production.

2. Copy the URL and the token

The token is shown only once. Copy it now.

3. Configure the contact point in Grafana

1

Alerting → Contact points → Add contact point

Name: aciona-me. Integration: Webhook.
2

URL

https://ingress.aciona.me/webhooks/<alertSourceId>
3

HTTP Method

POST
4

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 the severity label.

6. Set up automatic resolution

“Disable resolved message” must stay off, both on the contact point and on the notification policy. With it on, Grafana does not send resolved items and aciona.me has no way to close the incident — it stays open indefinitely.
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 a service label to your alert rules with the exact service name in aciona.me:

Troubleshooting

“Disable resolved message” is on somewhere — contact point or notification policy. Turn it off in both.
The X-Aciona-Token header is missing or wrong. If the token was rotated, update the contact point.
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.
The fingerprint is changing between triggers — usually because the rule’s labels change. Stabilize the labels that make up the alert’s identity.

More fixes