API referenceLogs, drains and alerts
Acknowledge an alert
Mark an open alert as being handled. PagerDuty and Opsgenie destinations are acknowledged too.
Authorization
bearer AuthorizationBearer <token>
In: header
Path Parameters
id*string
Match
^alt_[a-z0-9]{8,40}$Response Body
application/json
application/json
curl -X POST "https://example.com/v1/alerts/string/acknowledge"{ "object": "alert", "id": "string", "rule_id": "string", "rule_name": "string", "metric": "error_rate", "severity": "info", "status": "triggered", "subject": "string", "title": "string", "message": "string", "value": 0, "threshold": 0, "count": 0, "started_at": "2019-08-24T14:15:22Z", "last_seen_at": "2019-08-24T14:15:22Z", "acknowledged_at": "2019-08-24T14:15:22Z", "acknowledged_by": "string", "resolved_at": "2019-08-24T14:15:22Z", "resolved_reason": "auto", "muted": true, "timeline": [ { "at": "2019-08-24T14:15:22Z", "type": "triggered", "message": "string", "destination_id": null, "actor": null } ]}Provider status GET
Live health per provider: vendor failures in the last 30 seconds (the router's outage signal), last-hour error rate and latency, and 24-hour and 30-day uptime with daily bars.
Connect an alert destination POST
Connect email recipients (with optional hourly or daily digests), a webhook endpoint, a Slack or Discord incoming webhook, a Microsoft Teams Workflows URL, a PagerDuty Events API v2 integration key or an Opsgenie API key. The secret is stored encrypted in the vault and never returned.