What Sentry is
Sentry is an error and performance monitoring tool. It captures exceptions from your application with stack traces, breadcrumbs and the user's context, groups them into issues, alerts on new or rising ones, and traces slow requests. It is the source of truth for what went wrong in the code, and Vesqo does not try to replace any of that.
What Vesqo is
Vesqo is a business observability tool for SaaS companies: it reads Stripe, PostHog, GitHub, Sentry, support and CRM together and writes up what changed, which paying customers it hit, and what it costs. It reads Sentry as one of its sources.
The same questions, put to both
| Question | Sentry | Vesqo |
|---|---|---|
| What broke | Every exception, grouped into issues, with the stack trace, breadcrumbs and release. | The hourly error count and the new issues, read from Sentry. For the trace, open Sentry. |
| When it started | First seen, and the release the SDK stamped. | Dated to the release in GitHub or GitLab, and set against the same hours the week before. |
| Who it hit | User ids and emails on the events; a count of affected users. | The paying customers behind those users, by account, with what each pays. |
| What it costs | Not a question Sentry asks. | The MRR of the customers in it, and the payments that failed in the window, from Stripe. |
| What else moved | Performance and errors of the same application. | Checkouts in PostHog, conversations in the inbox, payments in Stripe, in the same hours. |
| Who is told, and how | Alert rules per project: email, Slack, PagerDuty and the rest. | A critical signal the minute it is written; everything else in one morning brief, ranked by money. |
| Fixing it | Assign, resolve, link the commit, see it come back. | Open the issue in Linear, Jira or GitHub with the write-up in it; ask follow-up questions. |
Using both
Connect Sentry to Vesqo with the one-click integration, or a user token with read scope. Tag events with the user's email in the SDK (Sentry.set_user) so Vesqo can name the customers, and set the release so a spike is dated even without GitHub connected.
Keep Sentry's alerting for the engineer on call, who needs the trace. Let Vesqo write the founder's version: three customers, €798 a month, roll back first.
Which, when
Sentry
You need to debug: the trace, the breadcrumbs, the exact line. Sentry, always.
Vesqo
You need to decide: whether this matters, to whom, and what it costs. Vesqo, reading Sentry.