Sentry
Connect Sentry to surface errors, performance issues, and crash reports in Cortex for faster incident resolution.
Overview
| Auth method | OAuth 2.0 (Sentry Integration) |
| Scopes | org:read, project:read, event:read, alerts:read, member:read |
| MCP support | Yes |
| Setup time | ~10 minutes |
How to connect
- Navigate to Settings → Integrations → Connectors
- Click Connect on the Sentry integration
- Authorize the Cendriix integration on your Sentry organization
- Once authorized, error data becomes available to Cendriix agents
Admin setup (self-hosted)
If you’re running Cendriix on your own infrastructure, an admin needs to:
- Create a Sentry Integration at Settings → Developer Settings → New Internal/Public Integration in your Sentry organization
- Set the redirect URL to:
https://api.<your-domain>/v1/connectors/sentry/oauth/callback - Enable the scopes listed above
- Store the credentials in AWS Secrets Manager at
cendriix/prod/connectors/sentry:{ "client_id": "...", "client_secret": "..." }
Capabilities
Once connected, Cendriix agents can:
- Read error events and stack traces across your projects
- Access performance transaction data
- View alert rules and triggered alerts
- Reference error context when debugging or generating fixes
Scopes explained
| Scope | Access |
|---|---|
org:read | Organization structure and membership |
project:read | Project configuration and settings |
event:read | Error events and stack traces |
alerts:read | Alert rules and incidents |
member:read | Team member information |
Security notes
- Sentry tokens support refresh for long-lived integrations
- Sentry does not expose a programmatic revocation endpoint — revoke by removing the integration in Sentry settings
- Disconnect at any time from Settings → Integrations → Connectors
Further reading
Last updated on