The community submitted 88 reviews to tell
us what they like about Sentry, what Sentry can do better, and
more.
4.9
Based on 88 reviews
Review Sentry?
Reviewers mostly see Sentry as a practical way to catch production issues fast, with useful stack traces, breadcrumbs, release context, user impact, and solid grouping and filtering. Users say it often helps them reproduce bugs on the first try and works well across frontend and backend setups. Makers of GraphBit, Greta, and Construct Computer echo that, praising real-time visibility and unified traces. The main complaints are early alert noise, source map setup, and gaps for some mobile or browser-extension workflows.
We run Sentry on both frontend (Next.js) and backend (Fastify/Node). The moment something breaks in production — a failed match update, a broken PDF export, a crashed worker — we know before any user reports it, with the exact stack trace and user context. For a two-sided app handling real-time sports scheduling, that peace of mind is invaluable.
What needs improvement
Honestly, the alert fatigue can be real early on — you need to tune noise filters or you'll drown in minor warnings. Source maps setup also takes some care to get right (we disabled them for now to keep builds clean).
vs Alternatives
We evaluated Datadog and LogRocket, but both felt like overkill for our stage. Sentry does error monitoring, performance tracking, and alerting in one integration — no extra infra, no extra cost. It just works out of the box with Next.js and Node.
It tells me which release broke it and which users hit it, which is the difference between an error log and something I can fix before anyone writes in. Breadcrumbs plus a source mapped stack trace usually gets me a reproduction on the first try instead of guessing from a screenshot, and for a small team that's most of the value.
What needs improvement
Out of the box it's noisy, and the first week is mostly tuning out browser extension errors and network blips before an alert means anything. That matters more than it sounds, because people stop reading alerts they've learned to ignore, which is worse than having none. Source maps also fail quietly on deploy, so the trace drops back to minified and nothing tells you until you're staring at it mid incident.
While Sentry offers a strong set of integrations and has been valuable in our stack, we ran into challenges when it came to managing bug tracking across native mobile codebases and setting up browser extension support for web apps. Our team was also handling backend service monitoring and analyzing app store reviews—all of which had us relying on multiple tools like Instabug, Firebase Analytics, and AnecdoteAI alongside Sentry.
FusionSuite.io offered us a more unified approach. It consolidated several of these capabilities into a single platform, which helped reduce complexity and overhead. The setup was smooth, and one of the practical benefits was the ability to define access roles and permissions tailored to Dev, QA, and Product team needs. That structure helped us stay aligned and better manage day-to-day execution across teams.
Sentry is a powerful error-tracking and performance-monitoring tool, available both self-hosted and in the cloud. It helps developers quickly detect, diagnose, and fix issues, improving application stability and efficiency. A must-have for seamless debugging
I like how app errors are collected and visible on the dashboard, grouping and filtering capabilities is very useful. I can monitor the issue and integrate it with all necessary platforms.
At "We Are Learning," Sentry has been a cornerstone for real-time error monitoring, significantly enhancing our debugging efficiency and system stability. Its real-time error capture, coupled with rich contextual data, has enabled us to identify and resolve issues with remarkable speed and accuracy. The seamless integration with our existing tech stack, including Microsoft Azure, ensures that our DevOps and development teams receive immediate notifications for prompt action. However, one area for improvement could be the inclusion of machine learning algorithms to predict potential system failures based on error patterns, which would allow for more proactive issue resolution. Overall, despite this room for enhancement, Sentry remains a crucial tool in our arsenal for maintaining a high level of service reliability and operational excellence.
Sentry is critical for Termdock and our backend services across error monitoring and performance tracing. Its issue grouping and release tracking let us map multi‑project, multi‑workspace events to the correct versions. Source Maps and Stack Traces speed up debugging, while Performance tracing visualizes slow transactions and bottlenecks. With alert rules and environment tags, we can quickly pinpoint issues in a terminal‑driven workflow and trace them back to the corresponding commit.
We evaluated New Relic, Datadog, and Firebase Crashlytics. They excel at broad observability and mobile crash reporting, but we prioritize consistent frontend‑backend error context, fine‑grained release/environment segmentation, and a developer‑friendly debugging experience. As a result, we chose Sentry as the core to ensure stability, speed, and traceability when multiple projects run in parallel.
We chose Sentry because production errors need context, not just logs. Its stack traces, release visibility, and issue grouping help us understand what broke and fix customer-facing problems quickly.