Sentry usage: errors, transactions and replays per day
See how many errors, transactions, replays and other events Sentry accepted each day, next to your other bills, so a noisy release shows up in the numbers.
What Burnstack tracks
- Accepted events per day and category (errors, transactions, replays, attachments, profiles and more) from Sentry's stats API (Sentry API). Accepted is what counts against your quota; filtered and rate-limited events aren't included
- Up to 90 days of history, the most Sentry's stats serve
- No dollar amounts. Import your Sentry invoice as CSV to add the cost
Alerts
- Spend alerts don't apply, because there are no dollar amounts. Burnstack still tells you when Sentry's data stops syncing.
The key you'll need
Your organization's slug and a token with Organization: Read (org:read, Sentry docs), pasted as org-slug:token. An internal integration token (Settings → Developer Settings) is best: it belongs to the organization, so it keeps working when someone leaves. A personal token with org:read works too. Organization tokens (sntrys_) only carry CI scopes and are refused.
Burnstack checks the key with Sentry, shows the account it belongs to when Sentry lets the key see it, and stores it in your computer's keychain (macOS Keychain or Windows Credential Manager). It only reads billing and usage.
Connect it: Sentry
Need
- Key: Organization slug and auth token
- Plan: Any plan. Sentry reports event counts, not dollars: import invoices for costs.
- Permissions: Organization: Read (org:read)
Paste your organization slug and a token joined by a colon: acme:token (the slug is in your Sentry URL). Create an internal integration under Settings → Developer Settings with only Organization: Read, or a personal token with org:read. Organization tokens (sntrys_) can't read stats. EU organizations are found automatically; for self-hosted Sentry, put its URL in front: https://sentry.example.com:acme:token. Sentry reports event counts, not dollars.
Steps not yet verified
- Open Settings → Developer Settings → Create New Integration → Internal Integration.
- Name it Burnstack; under Permissions set Organization to Read, everything else No Access.
- Save Changes and copy the token the integration gets.
- Paste ORG_SLUG:token into Burnstack (the slug is in your Sentry URL).
Paste it
In Burnstack: Connectors → Sentry → Add key → paste → Validate & save. The key goes straight into your computer's keychain.
If it fails
- Organization tokens (sntrys_) can't read stats
- Use an internal integration token with Organization: Read, or a personal token with org:read.
- Sentry API error 403
- The token lacks org:read. Set Organization to Read on the integration (or create a personal token with org:read).
- Sentry API error 404
- Check the organization slug in front of the token; for self-hosted Sentry put its URL first.
Let your AI do the clicking not yet verified
Paste this into an AI assistant that can use your browser, such as Claude in Chrome. It opens Sentry's key page and sets only the permissions above, then stops before the final button that creates the key.
Open https://sentry.io/orgredirect/organizations/:orgslug/settings/developer-settings/ in my browser. Choose 'Create New Integration', then 'Internal Integration'. Name it 'Burnstack'. Under Permissions set Organization to Read and leave everything else at No Access. Don't add webhooks, alert rules or other settings. Also tell me my organization slug from the URL; it isn't secret. Sentry has no expiry setting for this token, so skip that. Stop before clicking 'Save Changes' (the final button that creates the token) and tell me it's ready. I'll click it, copy the token and paste it into Burnstack myself. Don't copy, read or paste the token, and don't grant broader access or change any other setting. If Sentry asks me to sign in or confirm with 2FA, wait for me.
The key never passes through the AI: you click that last button yourself, copy the key and paste it into Burnstack.
What you'll see
- Usage + invoice import: Sentry reports usage, not dollars: Burnstack shows the usage, and the cost comes from Sentry invoices you import.
- History: 90 days (Sentry's longest stats period).
- Delay: Today's counts are partial and replaced at the next sync.
Good to know
- Why no dollars: Sentry's prices are volume-tiered, every paid plan includes a monthly quota, and many organizations prepay reserved volume at other rates (Sentry pricing). The API doesn't say what your plan includes or what you reserved, so a price per event would overstate most bills.
- No split per project.
- Self-hosted Sentry works too (put your server's address in front), as volume trends.
- Today's counts are partial until the next sync.
One bill, not a dashboard per vendor
Burnstack puts Sentry next to the rest of your spend and lets you group it by product with applications. Other integrations: Vercel, Neon, Supabase, OpenAI, Anthropic, GitHub, OpenRouter, DigitalOcean, Twilio, Stripe fees, Cloudflare, Netlify, AWS, Datadog, Cursor, PlanetScale, Azure, Google Cloud, MongoDB Atlas, Railway, Render, Heroku, Akamai (Linode), Vultr, Fastly, Runpod, xAI, Together AI, fal.ai, Runway, Upstash.
Sentry questions
Why doesn't Burnstack show Sentry costs?
Does it work with Sentry's EU region?
us: or de: in front of the slug.Start watching back.
Five minutes to connect your first vendor. Free for Mac, forever, and every byte stays yours.