Sentry

Sentry context enriches an existing Pulse. It does not create Pulses.

How this helps triage: matching excerpts can show up in the summary, the first checks, and What informed this on the Pulse.

Exhale uses a Sentry auth token at triage time to attach organization issue excerpts when an org is configured.

This is not issue/alert webhook ingest. If Sentry issues should become Pulses, connect Sources → Sentry.

Connect

1. Sign in as a workspace admin.
2. Open Connections → Context → Observability context → Sentry.
3. Save the auth token and organization slug, then Test connection.
4. Test connection to mark the connector configured.

See Sentry's official guide: Auth Tokens.

Missing credentials, timeouts, or vendor 403s skip this block. Triage still completes. Send-test-alert Pulses skip live collectors.

Plan

Growth or higher.

Connector slots are shared across Context categories (markdown runbooks use a separate document cap). Tighten AI → Prompt → Context use if excerpts are noisy or too large.

API

Writes use the signed-in session and CSRF. Secrets are never returned on GET.

Related

• Context index
• Prompt → Context use