Incident.io
NativeIncident.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
-
Go to API Key Settings
Navigate to Settings > API Keys.
-
Add a new API key
Click Add New and name the key
Antimetal. -
Select permissions
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.
-
Create the key
Click Create, then copy the API key on the next page. It is only shown once.
-
Share the key with Antimetal
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.
Contact us via Slack or at support@antimetal.com.
Related integrations
Ingest incidents and alerts from PagerDuty.
Start investigations and triage alerts in Slack.
Correlate metrics, logs, and traces.