Sentry
Error monitoring, tracing and session replay for bugs in production
1/3Sentry is application monitoring for developers: an SDK in your code captures unhandled errors and crashes and groups them into issues carrying the stack trace, the release that introduced them and the users affected, so a bug arrives already diagnosed rather than as a support ticket. Around error monitoring it adds tracing and profiling for slow code paths, Session Replay for watching what a user did before the error, logs and metrics, and cron and uptime monitoring. Seer, its AI debugging agent, proposes root causes and fixes and reviews pull requests. Plans are priced by event volume rather than per seat, with unlimited users from the Team plan upwards, and it is open source and can be self-hosted.
- Error monitoring that groups crashes into issues with stack traces
- Tracing and profiling to find slow code paths and N+1 queries
- Session Replay shows what the user did before the error
- Cron monitoring and uptime monitoring alongside application errors
- Seer, an AI debugging agent, plus AI review on pull requests
- Logs and metrics in the same place as errors and traces
- Priced by event volume, with unlimited users from Team upwards
- Open source and self-hostable, with SDKs for many platforms
Based on what people have said
Every answer links back to the mentions it came fromWhat do people use Sentry for?
Users employ Sentry for error monitoring, tracing, and tracking issues that arise in production environments. It is also used to identify problems that were not visible during the development or testing phases, and some users integrate it with AI agents to assist in resolving errors.
8 mentions · @d4m1n · r/SideProject · @boltdotnew · @konig0000 · @Aditya_181105 · r/AI_Agents · and 2 more · Aug 2026
Are there any concerns regarding Sentry's performance or configuration?
Some users have reported issues with console noise and unnecessary network requests when SDKs are configured with invalid tokens. Others have noted that default priority levels for bugs can be confusing, and there are concerns about AI agents getting stuck in loops while retrying Sentry errors.
4 mentions · r/AI_Agents · Hacker News · r/nextjs · Aug 2026
Can Sentry be self-hosted?
Yes, Sentry is open source and supports self-hosting.
1 mention · @yoelfme · Aug 2026
What are the opinions on Sentry's pricing?
Opinions are mixed; while some users incorporate it into their production stacks, others have expressed a desire to avoid paying for the service.
2 mentions · @tpritha03 · @codestirring · Aug 2026
These summarise counts and dates only. Read the quotes themselves under what people are saying.
What people are saying about Sentry
61% neutral“Sentry has cron monitoring as a feature. It's pretty useful, though I probably wouldn't use it if Sentry didn't offer a bunch of other features.”
“bye bye sentry”
“brb attending a few errors in Sentry I saw from people testing it”
“Production stack: - Next.js - FastAPI - PostgreSQL - Redis - S3 - Docker - GitHub Actions - Sentry - AWS/GCP”
“Worth turning your fix into a permanent CI assertion rather than a one-line patch: intercept outbound requests in the E2E run and fail the build if anything hits Sentry/PostHog ingest endpoints at all, so if someone reintroduces a placeholder token later (config refactor, copy-pasted env template) it breaks the build instead of just adding noise back.”
“Or just use sentry or similar”
“Sentry is open source and you can self-host it 🤔”
“The server currently uses around 8 MB of memory on my machine.It’s deliberately not an observability platform or a replacement for Sentry. It receives events from your applications, sends native push notifications, and keeps them in a purpose-built mobile inbox.I use Elixir, so I built an integration for ErrorTracker.”
“I don't want to pay for Sentry.”
“- Sentry monitoring”
“using Sentry for that though since you asked”
“The moment you wire up 6 agents with 3 feedback loops is when you stop being able to see which agent is actually burning tokens on useful work versus which one is stuck in a validation loop retrying the same Sentry error.”
“Monitoring errors using tools like Sentry or Posthog.”
“We had hundreds of bugs, and Sentry’s default priority levels made no sense.”
“Debugging console noise in our Docker E2E stack, every page load fired a Sentry envelope POST to an unreachable host and a PostHog /ingest/array/<token>/config.js that 404’d. Cause: both SDKs check whether a DSN/token is *present*, not whether it’s valid.”
“and this is Sentry's (non) availability now”
“I hooked up Sentry, then when it emails me a new error I paste the link into an AI agent and it resolves it.”
“monitoring agent just opening sentry issues and calling it a day is painfully relatable”
“I know sentry seer does this, but I was thinking of building a basic version built-into val town”
“Does this plan to replace something like Sentry?”
“But I would install @sentry and use tracing for better e2e wins.”
“Your users might be hitting errors you never see. Turn on the @sentry connector in http://Bolt.new, then ask: "What errors have happened in the last 24 hours? How can we fix these?"”
“Monitoring → Sentry”
“Monitoring → Sentry”
“At the same time, CI, GitHub, and Sentry are better thought of as deterministic infrastructure or tools rather than agents. I think a strong architecture usually combines both: agents for ambiguous reasoning and tools/workflows for predictable operations.”