Concepts

The objects and states used by Acked.

Services

A service represents a system you monitor, such as an API, worker, or database. Each service routes alerts to one schedule.

Integrations

An integration accepts signals for one service. Each integration has a separate credential, so it can be rotated or revoked independently.

Every new service includes a default integration. Acked shows its ingest URL at creation and after rotation. The existing secret cannot be retrieved later.

Schedules

A schedule defines who is on call. It has a timezone and one or more escalation levels:

A level cannot page several users simultaneously. Adding users to one level adds them to its rotation.

An override replaces the scheduled user for a defined time window.

Priority and urgency

Priority classifies impact. Urgency controls notification behavior.

AxisValuesWhat it decides
Prioritycritical, high, medium, low, infoImpact and sort order.
Urgencyhigh, lowCritical or ordinary notification delivery.

When urgency is omitted, info uses low urgency and every other priority uses high urgency.

The life of an alert

StateWhat it means
notifyingA responder is being paged. Reminders continue until acknowledgement or the next escalation.
ackedA responder acknowledged the alert. Reminders and escalation stop.
resolvedA user or recovery signal closed the alert.
notificationAn info alert was delivered once and requires no acknowledgement.
unreachableNo responder could be selected, or the configured escalation passes completed without acknowledgement.

Use the alert timeline to distinguish an uncovered schedule from an exhausted escalation chain.

The ledger

Each state change writes an append-only ledger row in the same database transaction. Alert pages show alert-specific events; Audit shows the organization ledger.

Start with the ledger when troubleshooting delivery.