What Rocketgraph uses from Sentry
- Error events — Exceptions captured by
captureException, with stack traces and tags - Structured logs — Log lines sent via
Sentry.logger.info/warn/error()(the logs dataset) - Issues — Grouped error patterns with
firstSeen/lastSeenfor deploy correlation - Environments — Filter analysis to production, staging, or any environment
Setup
1. Create a Sentry Auth Token
- Go to sentry.io → click your avatar → User Settings
- Under Auth Tokens, click Create New Token
- Select scopes:
project:readandevent:read - Copy the token (starts with
sntrys_)
2. Connect in Rocketgraph
Go to rocketgraph.app/sentry and enter:- Organization slug — from your Sentry URL:
sentry.io/organizations/{org-slug}/ - Project slug(s) — one or more Sentry projects (e.g.
my-api,my-web,my-cli) - Auth token — the token from step 1
3. Select environment
After connecting, use the environment selector on the Sentry page to choose which environment to analyze (e.g.production, railway). This filters out development noise.
Deploy diffs
When you expand a deploy on the Sentry page, Rocketgraph fetches logs from before and after the deploy and shows:- New errors — Error templates that didn’t exist before the deploy
- Disappeared patterns — Errors that were fixed, or info logs that stopped appearing
- Behavior changes — Templates with unusual frequency or error rate shifts
- Volume diff — Total log, error, and warning counts before vs. after
Multi-project support
Connect multiple Sentry projects (e.g.lore-api, lore-web, lore-cli). The cross-service analysis scans all connected projects and identifies causal chains across services.
Events vs. structured logs
Sentry has two data streams. Rocketgraph fetches both and merges them:
Some errors only exist in events (exceptions), while some only exist in structured logs (explicit log calls). Rocketgraph merges both for complete coverage.