Skip to main content

​
Overview

The Sentry integration enables Steadwing to access error tracking and performance monitoring data from your Sentry projects. During root cause analysis, Steadwing correlates error patterns, stack traces, and performance issues with production incidents to identify the underlying causes.

​
Why Use Sentry with Steadwing?

Error Correlation

Link production errors to specific incidents automatically

Stack Trace Analysis

Analyze error stack traces to identify problematic code paths

Performance Insights

Detect performance degradation patterns before and during incidents

Error Trends

Identify error spikes and anomalies that correlate with incidents

​
Setup Instructions

​
Step 1: Create Sentry Auth Token

  1. Log in to your Sentry account at sentry.io
  2. Navigate to Settings → Account → API → Auth Tokens
  3. Click Create New Token
  4. Configure the token:
    • Name: Steadwing Integration
    • Scopes: Select the following permissions:
      • org:read - Read organization information
      • project:read - Read project details
      • event:read - Read error events and issues
  5. Click Create Token
  6. Copy the generated token (it starts with sntrys_)
Save your token immediately! Sentry only shows it once. If you lose it, you’ll need to create a new token.

​
Step 2: Connect Sentry in Steadwing

  1. Navigate to Steadwing Settings
  2. Find the Sentry integration card
  3. Click to expand the collapsible form
  4. Paste your Bearer Token in the bearer_token field
    • The field should show: sntrys_xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  5. Toggle the switch to Enable the integration

​
Step 3: Verify Connection

  1. Return to Steadwing Settings
  2. Confirm the Sentry integration shows as Connected
  3. Create a test incident to verify error data is being pulled correctly

​
How Sentry Integration Works

​
Data Collection

Steadwing queries Sentry for:
  • Error Events - All errors and exceptions logged in your projects
  • Issue Details - Stack traces, error messages, and affected users
  • Performance Data - Transaction traces and slow queries
  • Event Metadata - Tags, breadcrumbs, and environment information

​
Root Cause Analysis

When analyzing an incident, Steadwing:
  1. Queries Sentry for errors within the incident time window
  2. Identifies error spikes or new error types
  3. Analyzes stack traces to locate problematic code
  4. Correlates errors with deployments from GitHub
  5. Provides error context in the RCA report

​
Configuration

​
Required Permissions

The Sentry Bearer Token must have:
  • org:read - Read organization and team information
  • project:read - Access project configuration and settings
  • event:read - Read error events, issues, and performance data

​
Supported Features

  • Error event tracking across all projects
  • Stack trace analysis
  • Performance monitoring (transactions)
  • Issue grouping and fingerprinting
  • Custom tags and metadata

​
Limitations

  • Historical data limited to Sentry’s retention policy
  • Rate limits apply based on your Sentry plan
  • Source map access requires separate configuration

​
FAQs

Steadwing reads error events, issues, stack traces, and performance data. It does NOT access user PII, session replays, or modify any Sentry data.
Yes, when creating the auth token, you can scope it to specific organizations and projects instead of granting global access.
Currently, Steadwing supports Sentry SaaS (sentry.io). Self-hosted Sentry support is on our roadmap.
Auth tokens don’t expire unless manually revoked. If disconnected, simply create a new token and update it in Steadwing Settings.
Yes, the RCA report includes links to relevant Sentry issues, stack traces, and error events that were analyzed.
Need additional help? Please reach out to us at [email protected]