Skip to main content

Documentation Index

Fetch the complete documentation index at: https://opensre.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

OpenSRE 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 OpenSRE to append findings to incident summaries

​
Setup

​
Interactive CLI

opensre integrations setup incident_io

​
Environment variables

INCIDENT_IO_API_KEY=your-api-key
VariableDefaultDescription
INCIDENT_IO_API_KEY-Required incident.io API key
INCIDENT_IO_BASE_URLhttps://api.incident.ioOptional API URL override for tests or private routing

​
Verify

opensre integrations verify incident_io
Verification performs a minimal GET /v2/incidents request.

​
Investigation Behavior

When an alert includes an incident.io incident ID or URL, OpenSRE 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, OpenSRE can use action="list" to list live incidents.

​
Write-Back

OpenSRE does not create native timeline events. incident.io’s public v2 API supports editing incidents, so OpenSRE write-back uses: 
POST /v2/incidents/{id}/actions/edit
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.