UptimeUptime Wiki

Recently RESOLVED incidents.

Overview

A separate route rather than ?state= on /incidents because the snapshot genuinely carries two distinct collections (active_incidents and recent_resolved_incidents) with different retention rules. Collapsing them behind a query parameter would imply a uniformity that does not exist.

Parameters

Query Parameters
offset?integer

Index of the first item to return. Clamped to the collection length, so an offset past the end is an empty page rather than an error.

Range0 <= value
limit?integer

Maximum items to return. CLAMPED to 1000, not obeyed and not refused: a late-campaign save has thousands of hosts and serializing all of them would occupy the single tokio thread to produce a body nobody wants.

Range1 <= value <= 1000

Try the endpoint

GET
/api/v1/incidents/resolved

Code example

curl -X GET "https://example.com/api/v1/incidents/resolved"

Response example

{  "items": [    {      "id": 0,      "root_kind": "string",      "root_entity_id": 0,      "rack_id": 0,      "root_msg_key": "string",      "root_msg_args": [        {          "key": "string",          "text": "string",          "number": 0.1,          "is_number": true        }      ],      "symptom_kind": "string",      "symptom_msg_key": "string",      "symptom_msg_args": [        {          "key": "string",          "text": "string",          "number": 0.1,          "is_number": true        }      ],      "symptom_customer_id": 0,      "confirmed": true,      "causes": [        {          "root_kind": "string",          "entity_id": 0,          "rack_id": 0,          "msg_key": "string",          "msg_args": [            {              "key": "string",              "text": "string",              "number": 0.1,              "is_number": true            }          ],          "confidence": 0,          "confirmed": true,          "cleared": true,          "articles": [            {              "id": "string",              "title": "string",              "title_plain": "string"            }          ]        }      ],      "started_at_ns": 0,      "last_changed_at_ns": 0,      "resolved_at_ns": 0,      "affected_customer_ids": [        0      ],      "affected_host_ids": [        0      ],      "affected_host_total": 0,      "revenue_at_risk_per_hour_dollars": 0.1,      "max_sla_tier": "string",      "compliance_at_risk": "string",      "redundancy_promise_broken": true,      "band": "string",      "timeline": [        {          "at_ns": 0,          "kind": "string",          "detail": "string"        }      ],      "work_order_ids": [        0      ],      "channel_thread_id": 0,      "articles": [        {          "id": "string",          "title": "string",          "title_plain": "string"        }      ],      "hint_tier": 0,      "hint": "string",      "evidence": [        {          "label": "string",          "label_plain": "string",          "value": "string",          "value_plain": "string",          "detail": "string",          "detail_plain": "string",          "leading": true        }      ]    }  ],  "total": 0,  "offset": 0,  "count": 0}

Response body

200Recently resolved incidents
application/json

Wrapper for a paginated collection.

Every collection endpoint returns this. Unbounded collection responses are not an option: a late-campaign save has thousands of hosts, and serializing all of them would occupy the single tokio thread to produce a body nobody wants.

On this page