Resolve errors with max efficiency, not max effort. Get actionable insights to resolve the most important code-related issues. Track, debug, and resolve errors across any language or framework with tailored context to get to the root cause every time.
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.
See what the app was doing when the error occurred: user interactions, AJAX requests, debug logs, network requests, and more. When errors happen, Sentry can prompt users for feedback so you can compare their experiences to the data.
Get real-time visibility across releases to see core metrics like crash-free sessions, version adoption, and failure rate so you can see the moment a release starts to degrade and quickly take action.
Aggregate errors by details like HTTP request, hostname, and app version to see what’s new, a priority, or a trend.
Assign custom tags to reproduce the error environment specific to your application, business, and users.
Answer the most important questions: In which app release did the bug occur? Was it the kraken?
Just look at all the high-quality security
features all accounts get, regardless of plan.
Use Sentry to collect and process errors and performance issues from clients and
connected projects. We support all major platforms.
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.