Create Rootly Incident

Learn how to automatically create Rootly incidents when dbt™ runs fail in Bolt. This integration helps data teams track and respond to pipeline failures efficiently by connecting Bolt’s pipeline monitoring with Rootly’s incident management platform. Create Rootly incident when the following Bolt schedules fail.

---

​

What You’ll Get

When a run fails, Bolt automatically creates a Rootly incident containing:

• Incident title with schedule name and workspace
• Incident details including:
  • Direct link to Paradime run logs
  • Run ID and execution details
  • Start and end timestamps
  • Commands executed
  • Branch information
• Severity level based on your configuration
• Dedicated Slack channel for incident collaboration

---

---

​

Setup Guide

Set up Rootly incident creation for failed runs. Follow the steps below, and watch our interactive tutorial. Step 1: Gather Your Rootly Information

1. Generate API Key:
   • Follow Rootly documentation to generate API Key
   • Copy and save your API key securely
2. Find Your Severity ID:
   • Visit your Rootly severity configuration
   • Identify the severity level you want to use for data pipeline incidents

Step 2: Configure the Webhook

1. From the Bolt home screen, go to Templates
2. Click Incidents and select “Create Rootly Incident”
3. Fill in the following fields:
   • Select Schedules: Choose the schedules for which you want to trigger this webhook. Leave blank or select all for all schedules without filtering
   • API Key: Enter the API key you generated in Rootly
   • Severity Id: Enter the Severity ID from your Rootly configuration
   • Slack Channel Name: Enter the Slack channel name where this incident should be managed (e.g., #data-incidents)
4. Click “Connect”

Step 3: Test the Integration

1. Run a Bolt schedule manually that will fail (the webhook only triggers on failed runs)
2. After the run fails:
   • Check your Rootly dashboard for the new incident
   • Verify a Slack channel was created or the incident was posted to your specified channel
   • Confirm the incident contains all run failure details