Sentry Observability Platform
Term 49 of 68 in the ERPStack technical glossary
What is Sentry Observability Platform?
Sentry is an open-source application monitoring and error tracking platform that helps developers identify, diagnose, and resolve application bugs and database performance bottlenecks in real time.
Sentry Observability Platform at a glance
- Primary job
- Group thousands of raw exceptions into a handful of distinct issues with stack traces
- Release context
- Errors tied to a release and commit, so 1 deploy can be identified as the cause
- Source maps
- Uploaded at build time, so a minified browser stack trace maps back to real source lines
- Privacy duty
- Scrub personal data before sending — an error payload can otherwise carry 2 kinds of regulated data
- Built with
- Sentry wired into Next.js 16, React 19 and Node.js services, source maps uploaded by GitHub Actions at build time, releases tagged per Vercel or AWS deploy, traces joined to OpenTelemetry, TypeScript 5.9 throughout
- Numbers that matter
- Thousands of events grouped into a handful of issues; 1 release identifier per deploy; 0 personal data sent; 6 months of unscrubbed payloads is the classic incident; 2 signals to join, exceptions and traces
- Compare with
- Raw Node.js logs, or OpenTelemetry Observability traces without exception grouping
- Commonly paired with
- Next.js 16, React 19, Node.js services, GitHub Actions releases, Playwright 1.59 runs, OpenTelemetry Observability traces and GDPR scrubbing rules
- Sampling arithmetic
- Errors captured at 100%, traces sampled: a 10% trace rate on a service taking 1,000,000 requests a day still leaves 100,000 traces to search.
- Why scrubbing is urgent
- GDPR Article 33 allows 72 hours to notify a supervisory authority. An error payload that carried personal data for 6 months is a breach report, not a debugging convenience.
- Where it runs
- 1 SDK across Next.js 16, React 19 and Node.js services on Docker, Kubernetes, AWS or Vercel, with 1 GitHub Actions step uploading source maps and 3 signals to join — exception, trace, release.
How Sentry Observability Platform works in production
The ERPStack approach to Sentry Observability Platform
We integrate Sentry tracing inside Next.js pages and edge routers, providing real-time error alerts and performance reports for your production applications.
Frequently asked questions about Sentry Observability Platform
What does an Observability Platform for errors give you?
Grouping and context. Raw exception logs produce thousands of lines nobody reads; an Observability Platform of this kind fingerprints them into distinct issues, counts occurrences, records which users and releases are affected, and attaches the stack trace and request context. That converts noise into a small ranked list, which is the difference between knowing errors exist and being able to act on them.
Why does release tracking matter so much?
Because it answers the first question during an incident: what changed. An Observability Platform that associates each error with a release and commit lets a spike be traced to the deploy that introduced it in seconds. Without that association, the same investigation means correlating a graph against a deployment log by eye, which is slower and considerably less certain.
What must never be sent to an error tracker?
Personal or regulated data. An Observability Platform receives request bodies, headers and local variables by default, which can capture protected health information, cardholder data or credentials without anyone intending it. Scrubbing rules must be configured before the first production event, not after a review discovers that 6 months of exception payloads contain data governed by a regulation.
How does error tracking relate to distributed tracing?
They are complementary halves. An Observability Platform for errors tells you what broke and in which release; OpenTelemetry tracing tells you where time was spent across services for a given request. Linking them by trace identifier means an exception can be opened from the trace that produced it, which shortens the path from symptom to cause considerably.