Sentry
Connect Sentry to TraceX with a read-only auth token so investigations can tie a problem to the exact error, its stack trace and the release that introduced it.
Connect Sentry so TraceX can tie a customer’s problem to the exact error, its stack trace, and the release that introduced it.
Why connect Sentry
Section titled “Why connect Sentry”A customer says “it broke”. Sentry knows which exception, where in the code and since which release. With Sentry connected, TraceX matches the issue to the right error group, follows its stack trace into your code and lines it up with what shipped, which is often the fastest path to a root cause.
Before you start
Section titled “Before you start”In Sentry, create an auth token with the scopes event:read and project:read:
- User settings → Auth tokens, or
- Settings → Developer settings → Custom integrations → an internal integration for your organization (recommended, as it isn’t tied to one person).
Connect
Section titled “Connect”Open Integrations → Sentry and fill in:
| Field | Value |
|---|---|
| Auth token | scopes event:read, project:read |
| Organization slug | acme (from acme.sentry.io) |
| Region | optional: sentry.io, us.sentry.io or de.sentry.io |
TraceX checks the token with a real read, then stores it encrypted.
How TraceX uses it
Section titled “How TraceX uses it”- Finds the errors matching an issue, by message, time, user or request.
- Reads their stack traces and matches the frames to your code.
- Checks the release in which the error first appeared, and the changes that shipped just before it.
Example
Section titled “Example”[email protected] gets “Something went wrong” when she saves her profile.
TraceX finds a ValidationError for that user in Sentry, follows the top frame to
profile/serializers.py, and sees the error first appeared in the release that made
phone required.
Troubleshooting
Section titled “Troubleshooting”| Problem | What to check |
|---|---|
| The token check fails | The token needs event:read and project:read. Check the organization slug matches. |
| Errors aren’t found | Set the region if your organization is on us.sentry.io or de.sentry.io. |
| Stack traces don’t match code | Connect the repository too, and make sure Sentry receives release and source information. |
Remove access
Section titled “Remove access”Disconnect Sentry in Integrations and revoke the token in Sentry.