Skip to main content
Your alerts already fire. aciona.me makes sure they reach the right person, that someone takes ownership, and that the whole path is on the record. aciona.me sits between your monitoring tools and the people responsible for them. It receives the alert, figures out which service is affected, finds the responsible team and the person currently on call, opens an incident, notifies whoever needs to act, and escalates automatically if nobody responds.

​
Start here

Receive your first alert

From zero to your first acknowledged incident in about 10 minutes.

How aciona.me works

The full path from an alert to a resolution.

Connect your tool

Grafana, Prometheus, Datadog, CloudWatch, Zabbix, New Relic and generic webhook.

Core concepts

Organization, team, service, schedule, alert source and incident.

​
The problem it solves

In most teams the critical alert already exists — it just has no owner. It lands in a Slack channel at 3 a.m., nobody gets paged on their phone, nobody knows whether someone is already looking at it, and there is no record of who responded or how long it took. aciona.me replaces that with an explicit flow:
1

Alert received

Your monitoring tool sends the alert to an aciona.me alert source.
2

Responder identified

aciona.me resolves the affected service, the responsible team and who is on call right now.
3

Incident created

An incident is opened with its own severity, context and history.
4

Person paged

Notifications by email, push, Slack and Microsoft Teams — according to what you configured.
5

Response tracked

Acknowledgement, ownership, escalation and resolution all land on the timeline.

​
Explore the documentation

On-call

Schedules, rotations, timezones, overrides and escalation.

Incidents

Lifecycle, ACK, assignment and resolution.

Notifications

Email, push, Slack and Microsoft Teams.

Teams and services

Who answers for what.

Troubleshooting

Alert did not arrive? Start here.

Reference

Payloads, severities, statuses and limits.