Alert History

What It Does

Returns a paginated list of alert history entries sorted by trigger time (newest first). Each entry includes the alert type, trigger message, current lifecycle status, and timestamps for trigger, acknowledgment, and resolution. Supports comprehensive filtering: by status (pending/acknowledged/resolved), alert_type, rule_id, and time range (from/to as ISO 8601 timestamps).

Why It's Useful

Alert history is the foundation for incident management and operational improvement. Use it to conduct post-mortems (identifying what triggered, when, and how quickly it was resolved), calculate SRE metrics (MTTA, MTTR), and identify patterns that indicate systemic issues. Per Google SRE practices, regular review of alert history helps tune thresholds and reduce toil.

Use Cases

Parameters

Response Fields

Code Examples

curl "https://api.edgedns.dev/v1/alerts/history" \
  -H "Authorization: Bearer YOUR_API_KEY"

const response = await fetch(
  'https://api.edgedns.dev/v1/alerts/history',
  {
    headers: {
      'Authorization': 'Bearer YOUR_API_KEY'
    }
  }
);

const data = await response.json();
console.log(data);

import requests

response = requests.get(
    'https://api.edgedns.dev/v1/alerts/history',
    headers={'Authorization': 'Bearer YOUR_API_KEY'},
    params={

    }
)

data = response.json()
print(data)

Related Endpoints

External References

Learn more about the standards and protocols behind this endpoint.