Product analytics
BetaConnect Sentry to Sondola
What Sondola reads from Sentry: errors and crash-free sessions and users. Read-only, with the source and period beside every number.
In beta. You can connect it today and it is built to the vendor's documented API, but it has not yet run for long across many workspaces. Check its first readings against the tool itself.
Read-only. Sondola never changes your data in Sentry.
- Credential
- API key
- Refresh
- Twice a day
- How it connects
- Pick the metric
- Setup time
- About 4 minutes
What Sondola reads from Sentry
- Errors
- Crash-free sessions
- Crash-free users
What you need
- A Sentry organization Manager or Owner. Crash-free rates need release health turned on in your app's Sentry SDK.
Collection timing and the period a reading covers are separate. Check the source's data-through date as well as the metric's reporting period.
Connect Sentry in 4 steps
- Create an internal integration
In Sentry open Settings, then Custom Integrations, and press Create New Integration. Choose Internal Integration and give it a name such as Metrics read-only.
Sentry: internal integrations ↗ - Grant two read permissions
Organization: Read and Issue and Event: Read. Leave everything else at No Access, then save.
Organization permission: Organization: Read. Issue and event permission: Issue and Event: Read. - Copy the token
It is listed under Tokens on the integration's page. It belongs to the organization, not to a person, so it keeps working when people leave.
- Name the organization and region
Paste the organization slug from your Sentry address and pick the data region. Add a project ID to count one project only.
Enter credentials only in your Sondola workspace. Keep keys out of screenshots, public repositories and support messages.
What Sondola asks you for
Sentry, Settings, Custom Integrations, Create New Integration, Internal Integration. Organization: Read and Issue and Event: Read. Copy the token under Tokens.
The part before .sentry.io in your Sentry address.
sentry.io works for US data, and de.sentry.io keeps EU data in the EU. Your organization settings show the region.
Leave empty to count every project. A numeric ID, shown in the project's settings.
Secrets are stored encrypted in your workspace, in a vault kept separate from the application database. Sondola never shows them again.
Permissions
- Two read permissions: Organization: Read and Issue and Event: Read. Everything else stays at No Access.
- The token belongs to the organization, not to a person, so it keeps working when people leave.
Refresh and first reading
Twice a day. Most tools refresh once or twice a day, and every number shows when it was read.
Save and test reads one day of accepted errors. Errors are events Sentry accepted, not ones it filtered or rate limited. Crash-free rates are read for each whole week or month, never averaged from days.
Troubleshooting
The test passes but no reading appears.
Sentry is a Pick the metric source. A working connection produces nothing until you choose a metric and its period. Then check the metric's reporting period and the source's data-through date.
A number differs from Sentry.
Compare the definition, unit and reporting period with the same number in Sentry before treating a difference as an error. When a stored reading changes, its history keeps the old value, the new value and the reason.
Provider documentation
Readings missing or old? Read the setup and troubleshooting guide and the worked freshness example.
Related integrations
See your company clearly by Monday.
Apply in two minutes. Once you are in, your first numbers arrive minutes after you connect a tool.
Free for qualifying startups. Read-only.