Sentry & PagerDuty Integration Guide

Overview

Error monitoring and incident response are two sides of the same coin. Sentry detects what’s broken; PagerDuty ensures the right person knows about it immediately. This integration bridges that gap, eliminating the delay between error detection and team notification.

For engineering teams running production systems, this pairing solves a critical problem: critical errors discovered by Sentry can languish in a dashboard if no one’s actively watching. By connecting Sentry to PagerDuty, you ensure that high-severity errors automatically escalate to your on-call responders, triggering notifications via SMS, phone, Slack, or email depending on your escalation policy.

How the Integration Works

• Alert Routing: Sentry monitors your application for errors, exceptions, and performance degradation. When an issue meets your alert threshold, Sentry sends a webhook to PagerDuty with details about the error.
• Incident Creation: PagerDuty receives the alert and creates a new incident (or groups it with an existing one, depending on your configuration). The incident is assigned to the appropriate service and escalation policy.
• On-Call Notification: The on-call engineer for that service receives a notification through their preferred channel—Slack, SMS, phone call, or email—with a summary of the error and a link back to Sentry for investigation.
• Bidirectional Context: Engineers can acknowledge or resolve the incident in PagerDuty, and those status changes can be reflected back in Sentry, keeping both systems in sync.
• Customizable Thresholds: You control which Sentry alerts trigger PagerDuty incidents. You might route only critical errors, performance regressions above a certain threshold, or errors affecting specific services.

Key Features & Capabilities

• Automatic Incident Creation: High-severity errors in Sentry automatically create incidents in PagerDuty, eliminating manual handoffs and reducing mean time to response (MTTR).
• Rich Alert Context: PagerDuty incidents include the error message, stack trace, affected users, and a direct link to the Sentry issue detail page, so responders have the information they need without switching tools.
• Escalation Policy Integration: Route alerts to the correct team based on service ownership. Errors in your payment module go to the payments team; API errors go to the platform team.
• Noise Reduction: Configure Sentry alert rules to suppress low-priority errors from triggering PagerDuty incidents, preventing alert fatigue and keeping your on-call team focused on what matters.
• Incident Grouping: Related errors can be grouped into a single PagerDuty incident, so a spike in the same error doesn’t create dozens of duplicate alerts.
• Audit Trail: Every error-to-incident transition is logged, providing visibility into how issues flow from detection to response and resolution.

Setup Difficulty

Easy (5–10 minutes, no code required).

The integration is straightforward to configure. In Sentry, you create an alert rule that specifies which errors should trigger PagerDuty incidents (by severity, project, environment, or custom conditions). You then select PagerDuty as the action and authenticate with your PagerDuty account. Sentry will ask which PagerDuty service should receive the incidents. Once saved, the integration is live. No API keys to manage manually, no webhooks to configure by hand—Sentry handles the plumbing.

If you want to customize behavior further (e.g., route different error types to different services, adjust severity mappings, or add custom fields), you may spend an additional 10–15 minutes configuring alert rules, but this remains within the UI and requires no developer involvement.

Common Use Cases

• Production Error Escalation: Any error in your production environment automatically pages the on-call engineer, ensuring critical issues are addressed within minutes rather than hours.
• Performance Regression Alerts: Sentry can detect when response times degrade or error rates spike. Route these to PagerDuty to trigger a rapid investigation.
• Service-Specific Routing: Errors in your checkout flow go to the payments team; database errors go to the infrastructure team. Each team sees only the incidents relevant to them.
• Reduced MTTR: By automating the notification chain, you eliminate the time it takes for a developer to notice an error in a dashboard and manually alert the team.
• On-Call Visibility: On-call engineers know that every PagerDuty incident from Sentry represents a real, detected issue—not a false alarm or low-priority warning.

Alternatives & Workarounds

If the native Sentry-to-PagerDuty integration doesn’t fully meet your needs, consider these alternatives:

• Zapier or Make (formerly Integromat): These no-code automation platforms can connect Sentry to PagerDuty with additional logic. For example, you could filter alerts by environment, add custom fields, or route to different services based on error type. Setup takes 10–20 minutes and costs a few dollars per month.
• Custom Webhook Handler: If you need highly specific routing logic (e.g., route errors to different services based on a custom field in Sentry), you can build a lightweight webhook receiver that listens to Sentry events and calls the PagerDuty API directly. This requires a developer but offers maximum flexibility.
• Competing Products: If you’re not yet locked into Sentry, other error tracking platforms like Datadog, New Relic, or Rollbar offer similar PagerDuty integrations and may provide additional features (e.g., APM, infrastructure monitoring) that reduce the need for multiple tools.

Frequently Asked Questions

Does every Sentry error create a PagerDuty incident?

No. You control which errors trigger incidents through Sentry alert rules. You can filter by severity, project, environment, error type, or custom conditions. For example, you might only route errors marked as “critical” or errors affecting more than 10 users. This prevents alert fatigue and keeps your on-call team focused on actionable issues.

Can I route different Sentry projects to different PagerDuty services?

Yes. In Sentry, you create separate alert rules for each project and specify which PagerDuty service each should notify. This ensures that errors in your mobile app go to the mobile team, errors in your API go to the backend team, and so on.

What information does PagerDuty receive from Sentry?

PagerDuty incidents include the error message, stack trace, affected environment, number of affected users, and a direct link to the Sentry issue. This gives on-call engineers enough context to begin investigating without leaving PagerDuty.

Can I acknowledge or resolve a PagerDuty incident and have it update Sentry?

The integration primarily flows from Sentry to PagerDuty. While PagerDuty actions don’t automatically update Sentry status, you can manually mark issues as resolved in Sentry once the incident is addressed. Some teams use Slack notifications from both tools to keep everyone in sync.

Disclaimer

Integration features and capabilities may change as both Sentry and PagerDuty release updates. This guide reflects the integration as of the time of writing. Always verify current capabilities and setup steps on the official Sentry and PagerDuty documentation pages before implementing.