Skip to main content
The alert source is an external tool’s entry point into aciona.me. It defines which organization owns the alert and how the payload is interpreted.

​
Creating one

1

Open Alert sources and create a new one

Owners and admins can create sources.
2

Choose the type

The type determines which payload translator is used:Generic · Grafana · Prometheus · Zabbix · Datadog · New Relic · CloudWatch
3

Give it a clear name

Use something that identifies the real origin: Grafana - production, Datadog - checkout, CloudWatch - account 1111.
4

Copy the URL and the token

On save, aciona.me shows:
The token appears only once. If you lose it, you have to rotate it — which means reconfiguring the external tool.

​
Best practices

Keep Grafana - production separate from Grafana - staging. That lets you disable a noisy origin without taking down the others, and keeps the audit trail clean.
Store it like any credential: secret vault, environment variable, secret manager. Anyone holding the token can open incidents in your organization.
An inactive source rejects alerts with 403 without losing the history already ingested.

Now connect your tool

Step-by-step guides for Grafana, Prometheus, Datadog, CloudWatch, Zabbix, New Relic and generic webhook.