FINDING 01·Frontend / Next.js developers·1 source
Sentry's main-thread performance impact in frontend apps
Developers integrating Sentry into Next.js and other frontend frameworks report that Sentry negatively affects Total Blocking Time and main-thread performance, and workarounds (e.g. Web Workers) are non-trivial to implement.
Source
“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·Enterprise developers using Sentry integrations·1 source
Plugin/integration compatibility breaks on Sentry version upgrades
Third-party integrations (e.g. YouTrack plugin) break when Sentry releases major versions, and unmaintained plugins leave users without workarounds for extended periods.
Source
“It seems like sentry-youtrack plugin is not fully compatible with the latest Sentry 9 version. I've discovered at least three issues... the latest release was issued almost 2 years ago, therefore, I'm not sure this will be solved quickly.”
FINDING 03·Agencies, multi-tenant SaaS operators·1 source
Noisy, per-issue email alerts with no digest/summary option
Users with many clients or high error volumes are overwhelmed by one-email-per-issue notifications and cannot configure summary/digest emails, making Sentry impractical for multi-tenant or high-traffic setups.
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 SDK support (e.g. Qt/Android, iOS)
Developers building cross-platform mobile apps with non-mainstream stacks (e.g. Qt C++) find Sentry's native SDK lacking: crashpad is unsupported on Android and iOS support is absent, forcing them to look for alternatives.
Source
“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·Privacy-conscious developers, enterprise teams, solo founders·2 sources
Self-hosting Sentry is difficult and resource-intensive
Users across multiple years (2019–2026) consistently report that self-hosting Sentry is painful, prompting a wave of simpler self-hosted alternatives. The desire for on-premise deployment is driven by privacy, security, legal, and cost concerns.
Source
“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
“It's an installable error tracker that works with Sentry SDKs... pay-once: prep your hardware, run one command, and you'll be up and running in 10 minutes.”
FINDING 06·Indie developers, small teams, side-project builders·1 source
Sentry is too heavyweight / complex for simple error monitoring needs
A recurring theme across multiple years is that Sentry's full observability platform is overkill for developers who just want basic error tracking and uptime alerts. This drives users to build or seek lightweight alternatives.
Source
“I wanted a simple, reliable tool I could own outright, without surprise bills for overages.”
FINDING 07·Startups, indie developers, small SaaS teams·1 source
Surprise billing / unpredictable costs on Sentry's hosted plan
Users frequently cite unexpected overage charges as a key reason to seek self-hosted or pay-once alternatives. This pain appears consistently from 2024–2026, suggesting it remains unresolved.
Source
“I wanted a simple, reliable tool I could own outright, without surprise bills for overages.”
FINDING 08·Self-hosted Sentry operators·1 source
Self-hosted Sentry performance data not appearing (data pipeline issues)
Users running self-hosted Sentry report that even when events are successfully ingested (HTTP 200), the Performance page shows no data, indicating a gap in the self-hosted data pipeline or documentation. This issue was reported in 2026 against version 21.11.0.dev0.
Source
“前端上报到sentry看接口是成功了，但是performance页面没有数据 (Frontend reports to Sentry and the interface shows success, but the performance page has no data.)”