Skip to main content

Resolve Alert

developer
POST/v1/alerts/history/:id/resolve

Marks an alert as resolved, indicating the underlying issue has been fixed. Include resolution notes documenting what action was taken — this builds an organizational knowledge base for future incidents. The resolution timestamp is recorded automatically, enabling MTTR calculations. Only pending or acknowledged alerts can be resolved.

What It Does

Transitions the alert status to "resolved", records the resolution timestamp, and stores optional notes describing the fix. Calculates time-to-resolution from the original trigger time. Already-resolved alerts cannot be re-resolved. The alert rule remains active and will trigger again if conditions recur.

Why It's Useful

Resolution closes the incident lifecycle loop and is critical for operational metrics. MTTR (Mean Time to Resolution) is the gold-standard SRE metric — tracking it per alert type reveals which issues take longest to fix and where to invest in automation. Resolution notes serve as a runbook for future incidents, per Google SRE and PagerDuty incident management best practices.

Use Cases

DevOps Engineer

Certificate Renewal Confirmation

After renewing an SSL certificate via ACME/Let's Encrypt, resolve the expiry alert with notes: "Certificate renewed, new expiry: 2026-05-15".

Close the alert and document the specific action taken for audit trails.

SRE

Incident Runbook Building

Resolve alerts with detailed notes about the root cause and fix, creating a searchable knowledge base for similar future incidents.

Reduce MTTR for recurring issues by building institutional knowledge.

Operations Manager

SLA Compliance Tracking

Resolution timestamps enable automatic MTTR calculation for SLA reporting and executive dashboards.

Demonstrate operational efficiency with concrete time-to-resolution data.

Parameters

NameTypeRequiredDescription
domainstringRequiredAlert ID (path parameter). Optional JSON body with { "notes": "..." }Example: {"notes": "Renewed certificate via Let's Encrypt, verified chain is valid"}

Response Fields

FieldTypeDescription
resolvedbooleantrue if successfully resolved

Code Examples

cURL
curl "https://api.edgedns.dev/v1/alerts/history/:id/resolve" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d "domain={"notes": "Renewed certificate via Let's Encrypt, verified chain is valid"}"
JavaScript
const response = await fetch(
  'https://api.edgedns.dev/v1/alerts/history/:id/resolve?domain=%7B%22notes%22%3A%20%22Renewed%20certificate%20via%20Let's%20Encrypt%2C%20verified%20chain%20is%20valid%22%7D',
  {
    headers: {
      'Authorization': 'Bearer YOUR_API_KEY'
    }
  }
);

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

response = requests.get(
    'https://api.edgedns.dev/v1/alerts/history/:id/resolve',
    headers={'Authorization': 'Bearer YOUR_API_KEY'},
    params={
    'domain': '{"notes": "Renewed certificate via Let's Encrypt, verified chain is valid"}'
    }
)

data = response.json()
print(data)

Read the full Resolve Alert guide

Why it matters, real-world use cases, parameters, response fields, and how to call it from Claude, ChatGPT, or Gemini via MCP.

Read the guide →

Related Endpoints

Acknowledge Alert

Mark an alert as acknowledged with optional notes

Alert History

List triggered alerts with filtering by status, type, and time range

External References

Learn more about the standards and protocols behind this endpoint.

NIST Alerting GuidelinesAlerting Best Practices

Try This Endpoint

Test the Resolve Alert endpoint live in the playground.

Open in PlaygroundGet API Key