Rootly Integration
Sync TigerOps incident timelines, AI remediation actions, and root cause data with Rootly workflows. Accelerate incident response and automate postmortem preparation from first alert to resolution.
How It Works
Generate a Rootly API Key
In your Rootly account, navigate to Settings > API Keys and generate a new key with incident read/write permissions. Copy the key for use in TigerOps.
Configure the Integration in TigerOps
Enter your Rootly API key in the TigerOps integration panel. Select which Rootly services and environments map to your TigerOps monitored services.
Set Incident Declaration Rules
Define which TigerOps alert severities automatically declare a Rootly incident. Map TigerOps services to Rootly teams, environments, and incident types.
Timelines and Runbooks Sync
TigerOps pushes AI-generated timeline events and suggested remediation steps directly into the active Rootly incident, accelerating postmortem preparation.
What You Get Out of the Box
Automatic Incident Declaration
TigerOps automatically declares a Rootly incident when critical anomalies are detected, pre-populating severity, affected services, and an AI incident summary.
Timeline Event Injection
Every significant event TigerOps detects — metric spikes, deployment correlations, dependency failures — is injected as a timeline entry in the Rootly incident.
Runbook Execution Sync
When TigerOps suggests and executes an AI runbook step, the action and outcome are recorded in the Rootly incident timeline for full audit traceability.
Postmortem Data Population
TigerOps pre-fills Rootly postmortem templates with detected root cause, timeline of events, impacted metrics, and AI-generated contributing factors.
Bi-Directional Status Sync
When an incident is manually resolved in Rootly, TigerOps is notified and stops alert escalation. TigerOps resolution also closes the Rootly incident.
Team and Role Mapping
Map TigerOps service ownership to Rootly teams and roles. Incidents automatically assign the correct Rootly responders based on service-to-team configuration.
Rootly Incident Workflow Config
Map TigerOps services to Rootly teams and configure timeline sync behavior.
# TigerOps — Rootly Integration Config
integrations:
rootly:
api_key: "${ROOTLY_API_KEY}"
min_severity: critical
auto_declare: true
auto_resolve: true
sync_timeline: true
sync_runbooks: true
service_mappings:
- tigerops_service: "api-gateway"
rootly_service_id: "svc_abc123"
rootly_team_id: "team_platform"
rootly_environment: "production"
- tigerops_service: "payments-service"
rootly_service_id: "svc_def456"
rootly_team_id: "team_payments"
rootly_environment: "production"
postmortem:
template_id: "tmpl_xyz789"
auto_populate: true
fields:
root_cause: "{{ai_root_cause}}"
timeline: "{{incident_timeline}}"
impact: "{{affected_services}}"
timeline_events:
- include: anomaly_detected
- include: deployment_correlation
- include: runbook_executed
- include: incident_resolvedCommon Questions
Can TigerOps trigger Rootly workflows and playbooks?
Yes. TigerOps can trigger Rootly workflow automations via the API when it declares an incident. This allows Rootly playbooks — such as auto-paging on-call, creating war rooms, or posting to status pages — to execute immediately on TigerOps detection.
Will duplicate incidents be created if both TigerOps and a human declare a Rootly incident?
TigerOps checks for existing open Rootly incidents for the same service before creating a new one. If an incident already exists, TigerOps attaches its AI data to the existing incident rather than opening a duplicate.
How does TigerOps populate the Rootly postmortem template?
TigerOps maps its AI root cause analysis, incident timeline, impacted services, and metric data to the corresponding fields in the Rootly postmortem. The exact field mapping is configurable per Rootly postmortem template.
Does the Rootly integration support multiple Rootly environments?
Yes. You can configure separate Rootly environment mappings per TigerOps environment tag (production, staging, etc.), ensuring incidents are declared against the correct Rootly environment.
Can I use Rootly as the single source of truth and have TigerOps follow Rootly incident status?
Yes. In follow-Rootly mode, TigerOps will not auto-resolve an incident until the corresponding Rootly incident is closed by a human. This is useful for teams that require human sign-off before resolving customer-facing incidents.
Supercharge Rootly with AI Incident Intelligence
No credit card required. Connect Rootly in minutes. AI timeline data flows automatically.