All connectors

Sentry errors for every product, before customers notice.

See unresolved issues, error volume, and the loudest problems across all of your Sentry projects.

Sentry auth token with read scopes. One-click Sentry sign-in is on the way.

What LopeBase reads

For each Sentry project you match to a property, LopeBase reads three things from Sentry's API, all about unresolved issues and how loud they are right now.

  • Error summaryHow many unresolved issues the project has, how many events they sent in the last 24 hours, and how many users they have touched in total.
  • Top issuesThe 15 unresolved issues with the most events in the last 24 hours, each with its title, culprit, level, users affected, and a link back to the issue in Sentry.
  • Daily eventsEvents Sentry received per day for the last 14 days, for the project as a whole.

The 24-hour figures come from Sentry's hourly buckets, so they cover the last day only. The users figure is Sentry's running total for each issue.

How to connect it

One Sentry token can cover every project you run. You match each project to its property once.

  1. 01

    In Sentry, open your account settings, then API, then Auth Tokens, and create a personal token with project:read and event:read. Nothing else.

  2. 02

    In LopeBase, open Manage, then Connections, and pick Sentry under Monitoring. Paste the token.

  3. 03

    Match each project to its property, using the project as it appears in its Sentry address. Self-host Sentry? Add your Sentry address too.

A key that can see several projects can connect them all at once, or reuse the same key for a new property later. See Connect your tools.

What LopeBase does with it

LopeBase only reads issues and events. It never resolves, assigns, or changes anything in Sentry.

  • Error spikes on the timelineEach property's 30-day timeline marks a day with at least three times its usual error count, and at least 10 events, beside that day's deploys, failed builds, traffic swings, and outages.
  • The incident reviewOn Uptime, Review incidents reads 30 days of outages with each project's unresolved count and top issues, then says what went wrong and what to fix first. It uses AI credits.
  • Every table, one click awayOpen the connection to see the summary, top issues, and daily events as tables, for any property.
  • A broken connectionIf the token is revoked or expires, the connection shows under Needs attention, so a gap in the numbers never goes unnoticed.

Questions it answers

Sentry tells you everything about one error. LopeBase is for the view across every product, with the rest of each product beside it.

  • Which product is noisiest today?Unresolved issues and 24-hour events per project, without opening each Sentry project in turn.
  • Did that deploy break something?With GitHub on the same property, a failed build or a deploy run sits on the timeline next to the day errors jumped.
  • Was the outage caused by an error?With uptime checks on, the incident review reads outages and top issues together.
  • Which error reaches the most people?Top issues carry Sentry's users-affected count, so a rare error that hits many users stands out from a loud one that hits a few.
  • Is the spike hurting signups or revenue?The same property shows traffic and revenue, so you can see if a bad day cost anything.

What it does not do

  • No stack tracesIt reads counts and issue titles, not stack traces, breadcrumbs, replays, or performance traces. Those stay in Sentry, one link away.
  • No triageResolve, ignore, and assign in Sentry. The token only has read scopes, and LopeBase only reads.
  • Unresolved onlyResolved and ignored issues are left out of the summary and the top list.
  • No error alerts of their ownA rise in errors shows on the timeline and in the review, but does not send an alert by itself. Keep Sentry's own alerts for that.

The unresolved count reads up to 100 issues per project, which is plenty to tell a quiet project from a loud one.

Sentry questions

Something else? Contact us.

Does it work with self-hosted Sentry?

Yes. Add your Sentry address when you connect, and LopeBase reads from there instead of sentry.io.

Can I resolve issues from LopeBase?

Not today. The Sentry connector reads. Resolve issues in Sentry.

Which scopes does the Sentry token need?

project:read and event:read. LopeBase never needs write scopes for Sentry.

Can one token cover several Sentry projects?

Yes. A personal token reaches every project you can see, so connect it once and match each project to its property.

Why does the timeline not mark every busy day?

A day is marked only when it has at least three times the property's usual daily errors and at least 10 events, so a steady trickle never looks like news.

I use PostHog error tracking. Do I need Sentry too?

No. If PostHog records exceptions for a property, the incident review reads them, and the timeline uses them when no other error tracker is connected.

Put Sentry next to everything else.

Free for one property. No card.