API referenceLogs, drains and alerts
Resolve an alert
Close an open alert now; destinations that get resolve notifications are told. The rule's cooldown starts from here.
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/resolve"{ "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 } ]}List alerts GET
Alerts newest first: open (triggered or acknowledged) or resolved, with how often each repeated and its timeline of notifications.
Create an alert rule POST
Alert when a metric crosses a threshold over a window: error_rate, p95_latency, spend, budget_used, vendor_failure_spike, vendor_key_failing, billing_mismatch, cache_hit_rate, delivery_backlog, security_event or new_ip. Scope it to the workspace, a key, a vendor or a capability; route it to every destination or to chosen ones.