Skip to main content
HealOps can use incident.io as incident context during RCA. The integration can list live incidents, fetch full incident metadata, read incident updates, and append final findings to the incident summary through the supported incident edit API.

​
Prerequisites

  • incident.io account
  • incident.io API key with read access to incidents and incident updates
  • Write permission if you want HealOps to append findings to incident summaries

​
Setup

​
Interactive CLI

​
Environment variables

​
Verify

Verification performs a minimal GET /v2/incidents request.

​
Investigation Behavior

When an alert includes an incident.io incident ID or URL, HealOps makes the incident_io_incidents action available with action="context". That reads:
  • incident metadata from GET /v2/incidents/{id}
  • incident updates from GET /v2/incident_updates?incident_id={id}
If no incident ID is present, HealOps can use action="list" to list live incidents.

​
Write-Back

HealOps does not create native timeline events. incident.io’s public v2 API supports editing incidents, so HealOps write-back uses:
The action appends findings to the incident summary. Use action="append_summary" only after the RCA has useful findings or next steps ready to publish.