Skip to Content
Manage ResourcesAlerts

Alerts

Alerts are runtime records created when policies trigger.

Alerts API
See the exact alert routes, status filtering, delivery queries, and transition responses.
Destinations
Configure where alerts are sent, run destination tests, and inspect delivery history correctly.

Alert reads and lifecycle actions

  • GET /v1.0/alerts — list alerts, optionally filter with ?status=triggered
  • GET /v1.0/alerts/:alertID — read one alert
  • GET /v1.0/alerts/:alertID/deliveries — read delivery attempts
  • POST /v1.0/alerts/:alertID/acknowledge — mark as seen
  • POST /v1.0/alerts/:alertID/resolve — mark as resolved
  • POST /v1.0/alerts/:alertID/archive — move out of active views

Alert lifecycle

triggered → acknowledged → resolved → archived
StatusMeaningTypical action
triggeredPolicy threshold breached. Delivery is pending or complete.Investigate the cause.
acknowledgedAn operator has seen the alert.Work on a fix.
resolvedThe issue has been addressed.Verify the fix holds.
archivedAlert is closed.No further action needed.

What an alert contains

Each alert records the policy state at trigger time:

  • policy_id, event_id — which policy and event
  • period, aggregate, condition, threshold — the rule that fired
  • severity — the policy’s severity level
  • value — the aggregated value that crossed the threshold
  • count, min, max — rollup stats from the triggering bucket
  • triggered_at — when the policy evaluated and fired

Delivery investigation

After an alert is triggered, Chirpier delivers it to matching destinations. Each delivery attempt is recorded with:

FieldDescription
channelDestination type (slack, discord, telegram, webhook, email)
targetWhere it was sent (URL, email address, etc.)
statussent or failed
response_statusHTTP status code from the downstream provider
error_messageError details if delivery failed
created_atWhen the attempt was made

Use delivery history to answer:

  • Was the alert routed to any destination?
  • Did the downstream provider accept the delivery?
  • What HTTP status or error came back?
  • Was a test send successful?

Filter delivery reads with:

  • kind=alert — real alert deliveries
  • kind=test — destination test deliveries
  • kind=all — both, for debugging

Use kind=test immediately after testing a destination to verify the send succeeded.

For delivery target configuration, continue with Destinations.

Last updated on
PoliciesDestinations