Product health

Turn unresolved Sentry issues into scoped, reviewed work

A bug that has fired four hundred times this month should not have to compete with an opinion. Connect Sentry and Spectr keeps a read-only view of your unresolved issues and the trend behind them, across up to three Sentry projects at once - Sentry's convention is one project per service, and most products are several. Those numbers go into the next spec, dated and credited to Sentry.

How it connects

A read-only Sentry User Auth Token plus your organisation slug and data region. Not an Organization Auth Token - Sentry hard-codes those to a CI scope that cannot read projects or issues.

Before you start

Sentry cloud (US or EU) only. The EU region is Sentry's Germany host.

What Spectr reads from Sentry

Unresolved issues from the last 30 days: Read across every environment, with counts and the affected service. A staging-only error still surfaces, because a staging-only error is still worth a ticket.
Error trend: Daily counts from Sentry's project stats, summed across the projects you selected, so the shape of the problem is visible and not just its total.
One to three projects, merged: All selected projects merge into a single snapshot with a per-project floor, so one noisy service cannot crowd every quiet one off the list.

A person approves everything before it is published

Spectr generates specs and stories, then stops. Every story goes to a review page where you approve it, edit it inline, or reject it - individually or in bulk. Only approved stories reach an issue tracker. There is no auto-publish setting to switch on, because a backlog nobody read is not a saving.

Setting it up

In Sentry, create a User Auth Token ("Personal Token") with org read, project read, and event read scopes.
Note your organisation slug and whether your data lives in the US or EU region.
In Spectr, open the project, go to Integrations, choose Sentry, and enter all three.
Select one to three Sentry projects. Spectr runs an initial sync and merges them into one view.

Frequently asked questions

Why will my Organization Auth Token not work?

Sentry creates Organization Auth Tokens with a fixed CI-only scope that its own interface says cannot be changed, so such a token cannot list projects or read issues. Use a User Auth Token, or an internal-integration token.

Does Spectr store anything personal from Sentry?

No. Aggregate counts only, and both the exception message and the code path are scrubbed - a code path can carry a tenant or customer id, so it gets the same treatment as the message.