Sentry

Connect reliability evidence

Sentry gives Health and Engine the reliability evidence needed to understand whether errors, issue pressure, or transaction latency may be affecting customer behaviour. Connect it when the question begins with an incident, error spike, or slow transaction.

Go to setup ↓

---

What this connection helps you answer

• Which issues or transactions created the most pressure?
• Did reliability movement align with a product or billing decline?
• How many users were affected when usable user context exists?

Sentry can support general reliability analysis without identity data. User-level and account-level impact claims require usable identifiers on the relevant events.

Setup

1. In Sentry, open Settings > Developer Settings.
2. Copy the Organization Slug and Project Slug.
3. Create an internal integration or personal token with read-only access.
4. Grant organization, project, issue, and event read access.
5. Enter the slugs and token in Prolytics Connections.

Why this access is needed

• Organization read validates the workspace slug and lets OS reach the selected project.
• Project read confirms the exact project and its available data.
• Issue and event read supports error pressure, affected-user analysis, and failure timelines. OS validates these capabilities before saving the connection. If a required permission is missing, Connections identifies the affected access instead of accepting a source that cannot support its claims.

After connection

OS begins preparing the errors, issues, affected-user evidence, and transaction latency available in the selected project. Latency comparisons require transaction data. Affected-user analysis requires user context on the relevant events.

Missing user context limits identity-dependent conclusions. General reliability movement remains available, and Health keeps the limitation visible.

Investigate reliability impact ->