incident.io

TraceStax integrates with incident.io to automatically declare incidents when critical alerts fire. When a TraceStax alert triggers, an incident is created in incident.io with the alert details pre-populated. This gives your team a single pane of glass for both detection (TraceStax) and incident management (incident.io).

---

Setup

1. Create an API key in incident.io

   In incident.io, go to Settings → API keys → Create API key.

   Give it a name like “TraceStax” and select the Create incidents permission (read-only scopes are not sufficient).

   Copy the API key — it is only shown once.

2. Add the key in TraceStax

   In the TraceStax dashboard, go to your project → Integrations → incident.io → paste the API Key → Save.

Caution

incident.io API keys have write access to create incidents. Store the key securely and rotate it if it is ever exposed.

---

What happens when an alert fires

When an alert policy with incident.io configured fires, TraceStax:

1. Creates an incident in incident.io with:
   • Name — the TraceStax alert title
   • Summary — includes the project name, alert type, and a link back to TraceStax
   • Severity — mapped from the alert severity level
2. Posts a link to the created incident in the TraceStax alert feed

TraceStax does not automatically resolve incident.io incidents when the alert clears — incident resolution is managed by your team in incident.io.

Note

We recommend configuring incident.io only on critical severity alert policies. Use Slack or email for lower-severity alerts to avoid incident fatigue.

---

Troubleshooting

Incidents not being created

• Verify the API key has write permission for incidents. A read-only key will result in 403 errors.
• Check that your incident.io account is active and not in a trial that has expired.

Duplicate incidents

• TraceStax creates one incident per alert firing. If an alert fires repeatedly without resolving, multiple incidents may be created. Set an appropriate alert cooldown in your alert policy to prevent this.