Issues & support
Set up Sentry
Connect Sentry to make error tracking searchable — each issue becomes a document with its level, where it fired, how many events and users it hit, when it was first and last seen and its status, so “is that crash known” answers from the tracker itself and resolved issues keep answering “how did we fix X”. Read-only.
Before you start
- Sentry → User settings → Auth Tokens (an internal integration's token also works), with the org:read, project:read and event:read scopes — nothing else is used.
- Copy it right away — it's shown once. Only reads are ever issued; nothing is written back to Sentry.
- Documents → Sentry, enter Organization — the acme in sentry.io/organizations/acme — and paste the Auth token.
- Projects: optional project slugs as Sentry's URLs show them, one per line — blank syncs every project the token can see.
- Advanced: Server URL for self-hosted Sentry (blank means sentry.io); Search filter narrows the sync with Sentry's own search syntax.
- Choose access groups, Test, then Sync.
| Server URL | Only self-hosted Sentry installations need this — the address you open Sentry on. Blank uses sentry.io. |
|---|---|
| Search filter | Anything Sentry's own issue search accepts — is:unresolved, level:error, release:1.2 — scopes what syncs. Blank brings resolved history too, which is usually right: “how did we fix X” lives there. |
What comes in
- Each issue becomes a document titled with Sentry's short ID and the issue title — project, status, level, event and user counts, first and last seen, where it fired (the culprit), a link back to Sentry and the error message where Sentry carries one.
- Counts round to an order of magnitude (~1k, ~2M), so a firing issue doesn't need re-reading every sync just because a counter ticked up; the document refreshes when its status, its last-seen day or a count's magnitude changes.
- Individual events and stack traces are not read — the issue is the unit.
Access
Access is allow-only: the groups chosen on the source cover everything Sentry brings in — the source exposes no per-item viewers to mirror, so Sentry's own project permissions are not reflected here.
Caps: 20 projects and 2,000 issues per project — Sync notes a cap it hits, and issues that age past the cap stay searchable rather than disappearing. Resolved issues sync too, unless the Search filter narrows them out. A project the token can't read is skipped and noted rather than failing the whole sync, its existing documents kept. Test says how many projects it reached and names the first of them; it fails with a specific reason when the organization slug or the token is missing, or when Sentry rejects the token. Revoke access any time by deleting the token under User settings → Auth Tokens.
Last updated 20 Sep 2026