Rootly

TraceStax integrates with Rootly to automatically create incidents and kick off automated runbooks when critical alerts fire. When a TraceStax alert triggers, Rootly receives the alert details and can run your pre-defined incident response workflows.

---

Setup

1. Create an API key in Rootly

   In Rootly, go to Settings → API Keys → Generate new key.

   Give it a descriptive name like “TraceStax” and copy the generated key.

2. Add the key in TraceStax

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

Caution

Rootly API keys have access to create and manage incidents. Keep the key secure and rotate it via the Rootly settings page if it is ever exposed.

---

What happens when an alert fires

When an alert policy with Rootly configured fires, TraceStax creates a Rootly incident with:

• Title — the TraceStax alert title
• Summary — project name, alert type, and a link to the TraceStax alert
• Severity — mapped from the alert severity (critical → your Rootly critical severity, warning → medium)

Rootly then runs any workflows you’ve configured for that severity or incident type — including Slack threads, runbook assignments, status page updates, and stakeholder notifications.

Note

In Rootly, you can set up Workflows that trigger automatically when an incident is created via the API. This lets you automate your response playbooks without any manual steps.

---

Troubleshooting

Incidents not being created

• Confirm the API key is valid by checking Settings → API Keys in Rootly.
• Verify the alert policy has Rootly selected as a notification channel.

Wrong severity mapping

• Rootly severity names are configured in Settings → Severities. If your Rootly account uses custom severity names, the mapping may not match. Contact TraceStax support to configure a custom mapping.