Incident.io
Incident.io holds the narrative record of what your team already knows about an outage. Antimetal reads incident timelines, catalog entries, and schedules with a read-only API key so investigations start with that history rather than from scratch.
What Antimetal does with Incident.io
- Pull incident timelines into an investigation as prior context
- Read catalog types and entries to map services to owners
- Read schedules to know who was on call when something fired
- Surface earlier incidents that match the current failure signature
Connecting Incident.io
Prerequisites
- An Incident.io account with a Team subscription
- Permission to generate API keys
Navigate to Settings > API Keys.
Click Add New and name the key
Antimetal.Enable: view data like public incidents and organisation settings; view all incident data including private incidents; view catalog types and entries; view all incident data including private incidents and manage incident memberships; and read schedules.
Click Create, then copy the API key on the next page. It is only shown once.
Paste the token in the Antimetal UI.
Permissions and access
Antimetal uses a read-only API key scoped to incidents, catalog entries, schedules, and organization data.
All tenant data is processed in isolated environments. See security and compliance for details.
Related integrations
Need help?
Contact us via Slack or at support@antimetal.com.