Errors don’t exist in a vacuum. With full-stack monitoring, you can trace frontend errors caused by backend code (and vice versa). Being able to correlate your apm logs with distributed tracing means that you can understand how your stack reacts to your latest deploy or integrating a third-party service.
Humans are visual creatures. Software errors, not so much. Instead of your eyes slogging over logs, Sentry’s full stack monitoring shows you a complete picture of what’s frustrating your users. Now you can connect those user facing problems on the frontend to impacted services on the backend and fix what matters first.
Connecting issues to their root cause doesn’t have to be a guessing game. With full-stack monitoring, you get added context about the application state so you’re able to quickly understand the impact of specific problems. What’s more, all unhandled exceptions are automatically captured, with individual errors rolling up into larger issues.
You can get started for free. Pricing depends on the number of monthly events, transactions, and attachments that you send Sentry. For more details, visit our pricing page.
Sentry doesn’t impact a web site’s performance.
If you look at the configuration options for when you initialize Sentry in your code, you’ll see there’s nothing regarding minimizing its impact on your app’s performance. This is because our team of SDK engineers already developed Sentry with this in mind.
Sentry is a listener/handler for errors that asynchronously sends out the error/event to Sentry.io. This is non-blocking. The error/event only goes out if this is an error.
Global handlers have almost no impact as well, as they are native APIs provided by the browsers.