Sentry

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 Sentry fits in

What Sentry sees, quoted in the next spec.

Spectr syncs Sentry read-only: unresolved Sentry issues and the error trend. When it drafts the next spec it quotes those numbers with the date they were true, and the Product Health page shows every project's errors in one place.

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.

Setting it up

  1. In Sentry, create a User Auth Token ("Personal Token") with org read, project read, and event read scopes.

  2. Note your organisation slug and whether your data lives in the US or EU region.

  3. Enter all three on the Spectr project's Integrations tab, under Sentry.

  4. Select one to three Sentry projects. Spectr runs an initial sync and merges them into one view.

Frequently asked questions

Anything else? Email hello@crowdlinker.com and a person will answer.

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.

Can I track more than three Sentry projects?

Three is the cap per Spectr project. It is set where it is because merging more than that into one snapshot stops being a useful summary.

Related

Use case

Prioritise with numbers instead of whoever sounds most certain

Real error and feedback numbers from PostHog and Sentry, quoted with a date in your specs

PostHog

Read-only errors, survey feedback and feature-flag state, cited with a date in your specs

Jira

Publish stories as Jira issues, with sub-task nesting, and read their status back

Linear

Publish stories as Linear issues and keep their status and labels in sync

See all 20 integrations →

AI ProductOps for the entire team.

Start for free at spectr.pm
  • Free plan
  • No credit card to sign up
  • 30-day free trial on Starter