Documentation

How to get an alert into Acked, and what happens to it after.

Start here

• Quickstart — from a new account to a page on your phone.
• Sending alerts — the ingest API, the payload, deduplication and resolving.
• Concepts Services, schedules, integrations, priority and urgency, and what an alert does from arrival to resolution.
• Integrations by tool — Datadog, Prometheus Alertmanager, Grafana, email, and anything that can POST JSON.
• Outbound webhooks — the payload we send, how to verify the signature, and how retries work.
• The mobile apps — install, sign in, and the permissions that decide whether a page wakes you.
• Accounts and organizations — members, roles, plans, and what deleting actually does.
• Why didn't it page me? The order to check things in, and how to read the alert timeline.

Concepts, in one paragraph

A signal arrives at a service. The service points at a schedule, which decides who is on call right now. Acked opens an alert and notifies that person. If nobody acknowledges it before the step's wait elapses, it escalates to the next level. Every transition is written to an append-only ledger, so "what happened, and who did what" is answerable afterwards.

Missing something?

These pages cover the path from a new account to a verified page, and what to do when one does not arrive. If what you needed is not here, say so at support@acked.dev — that is how this list grows.