Sentry

“You can even send data to both Sentry and Epure so you can compare which one you prefer to use.It's completely free and open source, btw.”

“It uses object storage and supports traces, logs, metrics, and Sentry errors.”

“we have similar mess at work, app logs in one place, model traces somewhere else, errors in sentry and half the time the correlation is just timestamp guessing game. what do you use for grouping errors into issues, some kind of fingerprinting or you doing something else?”

“I set up a webhook in @ampcode's Orbs to receive new Sentry errors, and now I wake up to PRs ready to review. Even better, it's smart enough to know when a fix isn't necessary.”

“For anything under a few thousand req/day I just do Sentry for errors plus Healthchecks or UptimeRobot for "is it even up," and skip metrics entirely until something actually hurts.”

“for a small Django VPS, i’d keep it simple: Sentry for exceptions, uptime check, and journald logs. That catches most real failures without maintaining Grafana.”

“For people running smaller Django apps on VPSs, what do you use today? Prometheus/Grafana, hosted monitoring, logs/Sentry only, or something lighter?”

“We use Sentry internally and it has been great to track and resolve issues in the app with this beauty.”

“Anyone actually using Sentry Seer? How is it?”

“Looks like it might be much lighter than Glitchtip? I know "write it in Rust" is a meme, but for basic sentry features you can probably do much better than Django for resources.”

“Am i reading this properly? This replaces Sentry and is self-hosted instead?”

“use something like sentry on your backend so you can get notifications messaged to you via slack/discord or whatever, so if something like this happens you'll be notified.”

“Everyday at 8AM create me a summary xplainer of new bugs from Sentry that need attention.”

“– Datadog (enterprise teams)”

“Posthog, Sentry, a lot of apps that do this already. They provide session recordings and logs for errors etc.”

“Want to send fewer noisy errors to @sentry ? After talking to hundreds of customers, I keep seeing logs, counters, and expected 401s sent as Errors. Put those signals in the right place and, hey, you might save some $$ too.”

“What I do like from cursor is the possibility to select from a large amount of different models. And my experience is that the tip tier models from codex and Claude behave differently via cursor then if working with them directly.”

“• Sentry — 5k errors”

“\- Sentry is a deeper error tool than this and I'd say so on a sales call.”

“My very first proposal was to have Sentry for both backend and frontend but it was refused by the managment 2 years ago.”

“System/unexpected errors: something broke internally and the user can’t really do anything about it. These should be tracked with monitoring tools like Sentry and alert the developers.”

“You just add them to your site and you get exception logging with a brief recording that can show you what the user was doing (scrubbed of any data) — check rollbar, sentry, and other exception tracking systems. Don’t build your own.”

“Bring the code down. Have fable/astra walk you through debugging suites with Sentry.io, push it back up.”

“If Sentry shows up later, it already can't leak it.”

“Yeah, I think it's super hard to know which kind of environments that real user use, not sure if there are any way to get that (just like Sentry frontend sdk).”