Connect Sentry so Foggy can pull error details and recent events when investigating an alert or user-reported issue.Documentation Index
Fetch the complete documentation index at: https://docs.foggyhq.com/llms.txt
Use this file to discover all available pages before exploring further.
What Foggy can do
| Tool | Description |
|---|---|
| Issues | Search and read Sentry issues |
| Events | Read individual events (stack traces, breadcrumbs, tags) |
| Releases | Read recent releases and their associated issues |
| Alerts | Read alert rules and firing state |
Setup
Go to Connectors → Add Connector → Sentry and fill in the form.| Field | Required | Description |
|---|---|---|
| Name | Yes | Label for this connector (e.g. “Sentry-Production”) |
| Personal Token | Yes | Sentry → Settings → Account → API → Auth Tokens. Scopes: org:read, project:read, team:read, event:read, alerts:read. |
| Organization Slug | No | From your Sentry URL: sentry.io/organizations/<slug>/. Leave blank to auto-discover. |
| Sentry URL | No | Leave blank for SaaS. For self-hosted, enter your Sentry URL. |
Read-only. All scopes are read-only — Foggy cannot create, resolve, or mutate anything in Sentry.
Troubleshooting
- Auth error on first query — token is missing one of the five required scopes. Regenerate with all scopes checked.
- “Organization not found” — the org slug does not match your account. Check the slug in your Sentry URL, or leave the field blank to auto-discover.
- Self-hosted can’t reach Sentry — confirm the Sentry URL is reachable from the Foggy agent host. Foggy does not proxy through sentry.io for self-hosted targets.
Next steps
GitHub
Pair Sentry with GitHub to link errors to the commits that caused them.
Slack
Get investigation results where your team already talks.