Skip to main content

​
Introduction

The Sentry integration connects Rootly with your Sentry organization so teams can receive error and performance alert events as alerts in Rootly and automate incident response from application issues. With the Sentry integration, you can:
  • Ingest Sentry issue alerts and metric alerts as Rootly alerts
  • Automatically resolve Rootly alerts when Sentry sends a resolved event alert
  • Set notification targets and alert urgency directly from Sentry alert rule settings
  • Use alert workflows to create incidents and automate follow-up actions

​
Before You Begin

Before setting up the integration, make sure you have:
  • A Rootly account with permission to manage integrations
  • Admin access to your Sentry organization
  • The Rootly app installed in your Sentry organization

​
Installation

Install the Rootly app in Sentry

Navigate to your Sentry organization settings and open the Rootly app page:
https://sentry.io/orgredirect/settings/:orgslug/sentry-apps/rootly/
Make sure you are logged into Rootly as an admin, then click the Rootly app to install it.
Rootly app in Sentry organization settings
You must be logged in as an admin in both Sentry and Rootly to complete the installation.

Configure alert rules in Sentry

In your Sentry project, navigate to Alerts > Rules and create a new alert rule or edit an existing one.In the Actions section of the rule, select Send a notification via the Rootly integration.
Sentry alert rule with Rootly action

​
Alert Types

Rootly supports three Sentry alert types, each with different behavior.

​
Issue Alerts

Issue alerts are tied to specific Sentry issues and support automatic resolution. When Sentry sends a resolved event for an issue alert, Rootly resolves the corresponding alert. You can configure the following directly in the Sentry alert rule action settings:
  • rootly_notification_target — routes the alert to a specific Rootly resource for on-call paging. Format: type:id (e.g. EscalationPolicy:abc-123). Supported types: User, Group, EscalationPolicy, Service. Set to none to disable paging.
  • rootly_urgency — sets the alert urgency in Rootly using the ID of a Rootly alert urgency. If not set or invalid, no urgency is assigned.
Issue alerts support automatic resolution. When Sentry sends a resolved notification, Rootly resolves the corresponding alert automatically.

​
Metric Alerts

Metric alerts are threshold-based and do not support automatic resolution in Rootly. When a metric alert fires, Rootly creates an alert in the open state. You must resolve it manually or through a workflow.
Metric alerts do not support automatic resolution. Rootly will not resolve a metric alert when the threshold returns to normal — you must resolve it manually or via a workflow action.
Like issue alerts, metric alerts also support rootly_notification_target and rootly_urgency settings in the Sentry alert rule action configuration.

​
Issue (Legacy)

The issue resource type is a legacy format that is still supported but not recommended for new alert rules. New rules should use event_alert (issue alerts) instead.
If you have existing Sentry alert rules using the legacy issue resource type, they will continue to work. There is no need to migrate them unless you want to take advantage of features only available in the newer alert types.

​
Set Up Alert Workflows in Rootly

Once Sentry alerts are flowing into Rootly, configure an alert workflow to automate incident creation:
  1. In Rootly, navigate to Workflows and create a new workflow
  2. Set the workflow type to Alert
  3. Set the trigger to Alert Created
  4. Add a run condition: Source is Sentry
  5. Optionally add label conditions to filter by specific projects, environments, or issue types
  6. Add a Create Incident action
Rootly alert workflow for Sentry
Use the rootly_urgency setting in your Sentry alert rule to assign different urgency levels to critical vs warning alerts. You can then use urgency as a workflow condition to handle high-urgency alerts differently.

​
How Alerts Are Mapped

Rootly extracts the following fields from each Sentry alert type: Issue alerts: issue title, issue ID, issue URL, error type, level, and project name Metric alerts: alert title, alert ID, and web URL Labels for all types include level, type, project, and status where available.

​
Troubleshooting

Confirm the Rootly app is installed in your Sentry organization and that the alert rule has the Rootly action configured. Verify the alert rule conditions are being met by triggering a test event in Sentry.
This is expected behavior. Metric alerts do not support automatic resolution in Rootly. You must resolve them manually or configure a workflow action to resolve them based on a follow-up Sentry event.
Check that the value follows the type:id format exactly (e.g. EscalationPolicy:abc-123) and that the resource exists in Rootly. Setting the value to none explicitly disables paging. An invalid or missing resource will cause the notification target to be silently ignored.
Confirm the value is a valid Rootly alert urgency ID and that it belongs to your Rootly team. Invalid urgency IDs are silently ignored and no urgency will be assigned to the alert.

​
Uninstall

To remove the Sentry integration, open the integrations panel in Rootly and select Configure > Delete.