Sentry

Monitoring

Application error tracking and performance

Sentry provides the deepest application-level error tracking with code-level context, suspect commits, and session replay, helping developers fix bugs faster than any infrastructure-focused monitoring tool.

Sentry is an application monitoring platform focused on error tracking and performance. It captures errors with full stack traces and context, helping developers find and fix bugs before users report them.

Reviewed by the AI Tools Hub editorial team · Last updated February 2026

Founded: 2012
Pricing: Free / $26/mo Team
Learning Curve: Low to moderate. Installing the SDK and capturing errors requires just a few lines of code — most teams are up and running within an hour. Learning to use advanced features like custom fingerprinting, alert rules, Session Replay, and the Discover query builder takes a few days. The main ongoing effort is tuning noise: configuring which errors to ignore, setting up ownership rules, and managing alert thresholds so the team trusts Sentry notifications rather than ignoring them.

Sentry — In-Depth Review

Sentry is an application monitoring platform focused on error tracking and performance monitoring that helps developers identify, triage, and resolve software issues before they impact users. Founded in 2012 by David Cramer and Chris Jennings, Sentry started as an open-source Django error logger and evolved into a comprehensive monitoring tool used by over 100,000 organizations including Disney, Cloudflare, GitHub, and Atlassian. Unlike infrastructure-level monitoring tools like Datadog or New Relic that focus on servers and services, Sentry operates at the application code level, showing developers the exact line of code, stack trace, and user context that caused an error.

Error Tracking and Issue Management

Sentry's core strength is its error grouping and deduplication engine. When your application throws an exception, Sentry captures the full stack trace, breadcrumbs (a trail of events leading to the error), user context, browser/device information, and custom tags. It then groups similar errors into "issues" using fingerprinting algorithms, so you see one issue with 10,000 occurrences rather than 10,000 separate alerts. Each issue includes a timeline showing when it first appeared, when it regressed, and how many users it affects. The "Suspect Commits" feature links errors to specific git commits, often identifying the exact PR that introduced a bug.

Performance Monitoring and Tracing

Sentry Performance provides distributed tracing and transaction-level monitoring that shows how requests flow through your application. It measures web vitals (LCP, FID, CLS), tracks slow database queries, identifies N+1 query patterns, and highlights API endpoints with degraded response times. The "Trends" view surfaces endpoints that are getting progressively slower over time, catching performance regressions before they become user-visible. Unlike full APM tools, Sentry's performance monitoring is tightly integrated with error tracking, so you can see both errors and performance issues in the same context.

Session Replay and User Context

Session Replay records user interactions as a video-like reconstruction of their browser session, showing exactly what a user saw and did before encountering an error. This eliminates the "cannot reproduce" problem that plagues bug reports. Replays include DOM snapshots, network requests, console logs, and user clicks, all synchronized with the error timeline. Privacy controls allow masking sensitive data like form inputs and personal information. This feature bridges the gap between error monitoring and user experience tools like FullStory or LogRocket.

SDKs and Platform Coverage

Sentry supports over 100 platforms and frameworks through official SDKs: JavaScript (React, Vue, Angular, Next.js), Python (Django, Flask, FastAPI), Java, Go, Ruby, PHP, .NET, Rust, iOS (Swift, Objective-C), Android (Kotlin, Java), React Native, Flutter, and Unity. Each SDK is purpose-built for its platform, capturing platform-specific context like React component trees, Django middleware chains, or iOS crash reports with symbolicated stack traces.

Pricing and Self-Hosted Option

Sentry offers a free Developer plan with 5,000 errors and 10,000 performance transactions per month — generous enough for small projects. The Team plan starts at $26/month for 50,000 errors and 100,000 transactions. The Business plan at $80/month adds advanced features like custom dashboards, data forwarding, and extended data retention. Uniquely, Sentry is also available as a self-hosted open-source deployment using Docker Compose, though self-hosting requires significant DevOps effort and lacks some cloud-only features like Session Replay and advanced integrations.

Pros & Cons

Pros

  • Best-in-class error grouping and deduplication — consolidates thousands of occurrences into actionable issues with suspect commits
  • Generous free tier with 5,000 errors and 10,000 transactions per month, sufficient for small projects and startups
  • Over 100 official SDKs covering every major language, framework, and platform with deep, idiomatic integrations
  • Session Replay shows exactly what users experienced before an error, eliminating 'cannot reproduce' scenarios
  • Open-source self-hosted option available for organizations that need full control over their data
  • Suspect Commits and ownership rules automatically assign errors to the developer or team responsible

Cons

  • Performance monitoring is less comprehensive than dedicated APM tools like Datadog or New Relic for infrastructure-level visibility
  • Self-hosted deployment requires significant DevOps effort and misses cloud-only features like Session Replay
  • Alert fatigue can become a problem in noisy applications — requires investment in alert rules and issue assignment workflows
  • The volume-based pricing can become expensive for high-traffic applications that generate millions of events per month
  • Dashboard customization is more limited compared to dedicated analytics tools — complex queries require the Discover feature

Key Features

Error Tracking
Performance
Session Replay
Profiling
Alerts

Use Cases

Frontend Error Monitoring for Web Applications

Frontend teams use Sentry's JavaScript SDK to capture unhandled exceptions, failed API calls, and console errors in production. Source maps provide readable stack traces even in minified production code, and Session Replay shows the exact user actions that triggered the error.

Mobile App Crash Reporting

Mobile teams use Sentry's iOS and Android SDKs to capture crashes, ANRs (Application Not Responding), and handled exceptions. Symbolicated stack traces, device context, and release health metrics help prioritize which crashes to fix first based on user impact.

Release Health and Regression Detection

Engineering teams configure Sentry to track error rates per release, automatically detecting when a new deployment introduces regressions. The Release Health dashboard shows crash-free session rates, and alerts fire when a new release degrades stability below defined thresholds.

Backend API Error Triage for Microservices

Backend teams instrument Python, Node.js, or Go services with Sentry to capture server-side exceptions with full request context. Ownership rules route errors to the responsible team automatically, and integrations with Jira or Linear create tickets directly from Sentry issues.

Integrations

GitHub GitLab Bitbucket Jira Linear Slack PagerDuty Microsoft Teams Vercel Netlify Segment Datadog

Pricing

Free / $26/mo Team

Sentry offers a free plan. Paid plans unlock additional features and higher limits.

Best For

Developers Engineering teams Startups Mobile developers

Frequently Asked Questions

How is Sentry different from Datadog or New Relic?

Sentry focuses on application-level errors and developer experience, showing stack traces, suspect commits, and session replays. Datadog and New Relic focus on infrastructure and APM, monitoring servers, containers, and service-level metrics. Many teams use Sentry alongside Datadog or New Relic: Sentry for finding and fixing bugs in application code, and the APM tool for monitoring infrastructure health and system-level performance.

Is the self-hosted version of Sentry production-ready?

The self-hosted version is functional and used by many organizations, but it requires running PostgreSQL, Redis, Kafka, ClickHouse, and several Sentry services via Docker Compose. Expect to invest significant DevOps effort in maintenance, upgrades, and scaling. Self-hosted also lacks some cloud-exclusive features like Session Replay and certain integrations. Most teams start self-hosted and migrate to Sentry Cloud as their needs grow.

How does Sentry handle sensitive user data and privacy?

Sentry provides data scrubbing features that automatically redact sensitive data like passwords, credit card numbers, and API keys before they leave your application. Session Replay masks text inputs by default and allows configuring additional privacy rules. Sentry offers EU data residency, SOC 2 Type II compliance, and GDPR-compliant data processing. You can also configure server-side data scrubbing rules and set custom data retention periods.

What is the difference between Sentry's error tracking and performance monitoring?

Error tracking captures exceptions, crashes, and unhandled errors with full stack traces and context. Performance monitoring tracks transaction durations, web vitals, database query times, and API response times — things that are slow but don't throw errors. Together, they give a complete picture: errors tell you what is broken, performance tells you what is slow. Both share the same SDK, so you enable them together with minimal additional configuration.

Can Sentry handle high-traffic applications without impacting performance?

Yes, but you need to configure sampling. Sentry SDKs support configurable sample rates for both errors (e.g., capture 100% of errors) and performance transactions (e.g., sample 10% of transactions). This lets high-traffic applications control costs and SDK overhead. The SDK itself adds minimal latency — error capture is asynchronous and typically adds less than 1ms to request processing. For applications processing millions of requests per hour, setting an appropriate transaction sample rate is essential.

Sentry in Our Blog

Sentry Alternatives

Sentry Comparisons

Ready to try Sentry?

Visit Sentry →