Crowswatch
Sentry

Stack Monitors

Monitor Sentry Error Tracking with Crowswatch

Monitor error tracking, performance monitoring, and release health across your Sentry organisation directly from Crowswatch.

What This Integration Provides

  • Error tracking: issue count, error rate, and unresolved issue trends by project
  • Performance monitoring: transaction throughput, latency, and Apdex score
  • Release health: crash-free session rate and adoption per release
  • Alert rules: active metric and issue alert state
  • User impact: users affected by errors per project

Requirements

RequirementDetail
Sentry accountFree or above (self-hosted or cloud)
Internal Integration tokenOrganisation-level token with read scopes
Organisation slugYour Sentry organisation identifier
Estimated setup time~10 minutes

Step 1: Generate Credentials

Sentry supports several token types. Internal Integration tokens are the recommended approach for monitoring tools, as they are tied to your organisation (not a personal account) and support fine-grained permission scopes.

To create an Internal Integration:

  1. Log in to Sentry and go to Settings (organisation settings, not your personal settings)
  2. Navigate to Developer Settings → Internal Integrations
  3. Click Create New Integration
  4. Enter a name (e.g. crowswatch-monitor) and an optional webhook URL
  5. Under Permissions, set the following scopes to Read:
    ResourceScope
    Eventevent:read (read issues and error events)
    Projectproject:read (read project settings and stats)
    Organizationorg:read (read organisation details and members)
    Releaseproject:releases (read release and session data)
  6. Click Save Changes
  7. Scroll down to the Tokens section and click New Token
  8. Copy the token immediately
Personal auth tokens are available at the account level but are tied to your user account. Internal Integrations are preferred for shared monitoring setups.

Step 2: Locate Required IDs

Organisation slug

  1. In Sentry, go to Settings → General Settings
  2. The Organisation Slug is shown in the General section
  3. It is also visible in the URL: sentry.io/organizations/<slug>/

Step 3: Add Credentials to Crowswatch

Navigate to: Crowswatch → Add Service → Sentry

FieldValue
Auth TokenThe Internal Integration token from Step 1
Organisation SlugYour Sentry organisation slug

Available Metrics

Error Tracking

  • Total issues (unresolved)
  • New issues in the last 24 hours
  • Error event volume over time
  • Issues by project

Performance

  • Transaction throughput (transactions/minute)
  • P50 / P95 / P99 latency
  • Apdex score per project
  • Slow transaction count

Release Health

  • Crash-free session rate (%) per release
  • Session adoption (% of users on latest release)
  • Error rate by release version

Alerts

  • Active metric alert state (Critical / Warning / OK)
  • Recently triggered issue alerts

User Impact

  • Users affected by errors (unique user count)
  • Most impacted users per issue

Connect

  1. Enter your Auth Token and Organisation Slug
  2. Click Verify to confirm the credentials are valid
  3. Select the projects and metrics you want to track
  4. Click Connect

Security

  • Internal Integration tokens are scoped to your organisation and do not expose any personal account data
  • Use only the read level for each scope. The write and admin scopes are not needed for monitoring
  • Revoke the token at any time in Settings → Developer Settings → [your integration] → Tokens
  • Create a separate integration for each external tool you connect to Sentry

Troubleshooting

Authentication error

Verify the token is active, as tokens can be revoked from the internal integration settings. Confirm you are using the token value, not the integration ID.

Projects not appearing

Ensure the token has project:read scope. Confirm the organisation slug is correct, as it is case-sensitive.

Performance data missing

Performance monitoring must be enabled on the relevant Sentry project (Project Settings → Performance). Some performance metrics require the SDK to be configured with tracing enabled.

Release data not visible

Releases must be created in Sentry (either manually or via the release tracking SDK) for release health data to appear. Ensure project:releases scope is included in the token.

Wrong organisation

If you belong to multiple Sentry organisations, confirm the slug matches the organisation containing the projects you want to monitor.