FINDING 01·Frontend/full-stack developers using Next.js·1 source
Sentry's main-thread performance impact on web apps
Developers integrating Sentry into Next.js and similar frontend frameworks report that Sentry negatively affects Total Blocking Time and main-thread performance, and workarounds like Web Workers are difficult to implement correctly.
Source
“I'm working on a Next.js project where I want to set up Sentry for error tracking without impacting the Total Blocking Time (TBT) and main-thread performance. I've tried moving Sentry operations to a Web Worker, but I'm facing issues with Sentry events not being sent successfully.”
FINDING 02·Engineering teams using Sentry with project management tools·1 source
Plugin and integration compatibility breaks with Sentry upgrades
Third-party plugins (e.g., YouTrack integration) break when Sentry releases major version updates, leaving users without working integrations and with no timely fixes from plugin maintainers.
Source
“It seems like sentry-youtrack plugin is not fully compatible with the latest Sentry 9 version. I've discovered at least three issues: 1. Tricky combination of redis-py-cluster and redis: latest versions seems to be not compatible with each over out of the box. 2. Creation of new issues is broken due to absence of sentry/groups/details.html file. 3. The list of projects on YouTrack is not populated.”
FINDING 03·Agencies, SaaS teams managing multiple clients·1 source
Alert noise and poor issue grouping across clients
Users report that Sentry sends excessive per-issue, per-client emails and fails to deduplicate or group errors intelligently, making it impractical for multi-tenant or high-volume environments.
Source
“We have a lot of clients and whenever something is wrong on the clients, sentry sends one email per issue per client (because sentry is unable detect the issues being the same). I couldn't find it, but is sentry capable of sending summary messages every X minutes instead?”
FINDING 04·Mobile/cross-platform C++ developers·1 source
Limited mobile/cross-platform SDK support (e.g., Qt on Android/iOS)
Developers using non-mainstream stacks like Qt C++ on Android report that Sentry's native SDK does not support their platform correctly, with transport errors and no iOS support, forcing them to look for alternatives.
Source
“Sentry runs fine for the most part, but it outputs discarding envelope due to invalid transport instead of sending any events. Tried using crashpad, but it says it's unsupported on Android. In the future, I want to do logging on iOS as well which Sentry Native does not appear to support, so I am not against alternative frameworks if anyone knows of any.”
FINDING 05·Indie developers, small teams, privacy-conscious engineers·2 sources
Self-hosting Sentry is complex and resource-heavy
A recurring theme across multiple years (2019, 2022, 2024, 2025) is that self-hosting Sentry is difficult, heavyweight, or impractical for smaller teams. This has driven a wave of community-built alternatives explicitly focused on simpler self-hosting. The pain appears persistent and unresolved as of early 2025.
Source
“Bugsink is a error tracking tool with a focus on self-hosting and simplicity. Self-hosting may be important for privacy, security and legal reasons, or just because you have good taste. A focus on self-hosting should be contrasted with the 'Self Hosted In Name Only' approach of «coughs loudly».”
Source
“I wanted a simple, reliable tool I could own outright, without surprise bills for overages. Telebugs is built with Rails 8, Hotwire, TailwindCSS, and SQLite. Like 37signals' ONCE products (my inspiration), it's pay-once: prep your hardware, run one command, and you'll be up and running in 10 minutes.”
FINDING 06·Startups, indie developers, side-project builders·2 sources
Sentry's pricing causes surprise bills and cost unpredictability
Users building alternatives explicitly cite unexpected or uncontrollable costs as a key reason to leave Sentry. This is a live pain as of 2025, with multiple builders citing billing unpredictability as their primary motivation.
Source
“I wanted a simple, reliable tool I could own outright, without surprise bills for overages.”
Source
“Built a lightweight Sentry alternative in 10 days. How it is different from Sentry: Lightweight SDK, easy 2-line setup. Focus on error and uptime monitoring only. Useful if you just want to know when something breaks without setting up a full observability platform.”
FINDING 07·Self-hosted Sentry operators, DevOps engineers·1 source
Performance monitoring data missing or unreliable in self-hosted instances
Users running self-hosted Sentry report that the performance monitoring page shows no data even when error ingestion appears to be working correctly, indicating a gap between the hosted and self-hosted feature parity.
Source
“我们自建的sentry版本是Sentry 21.11.0.dev0，前端上报到sentry看接口是成功了，但是performance页面没有数据 (Our self-built Sentry version is 21.11.0.dev0, the frontend reports to Sentry and the interface is successful, but there is no data on the performance page.)”