4 ms·
I love Sentry but it has become a bit over-the-top complicated as of late (for my taste). Glad to see one more on the market. I only knew about GlitchTip prior
by jensenbox 1y ago
I love Sentry but it has become a bit over-the-top complicated as of late (for my taste).
Glad to see one more on the market. I only knew about GlitchTip prior to today.
- lawgimenez 1y agoTried Sentry, then went back to BugSnag again. For me Sentry is just too much for a single developer.
- valenterry 1y agoFor a single developer? What do you mean?
- stronglikedan 1y agoDon't get your hopes up.
- vanschelven 1y agoNot the parent but I imagine something like "the more software caters to big orgs, the worse fit it becomes for individuals"
- lawgimenez 1y agoSorry, what I meant was the features on BugSnag’s free plan is enough for me. I feel like Sentry caters more on their business customer.
- drcongo 1y agoAgreed. We use both Sentry and Bugsnag (or whatever terrible name it has now) on different projects, and over time Sentry's interface has gotten considerably worse while Bugsnags got slightly better. I don't know if Sentry is aimed at significantly different users to us (an agency with many projects, mostly Django), but the sheer information overload when trying to understand an error is so bad that I ended up building a tool that receives Sentry webhooks and displays the information in a logical, sparse and easily digestible way. Bugsink looks nice and straight forward, and if anything other than email - the absolute worst medium for notifications - lands in there I'll probably make the switch.
- jensenbox 1y agoWe use Datadog and Sentry because their mechanism of interaction and retention are different - if Datadog changed their process to be closer to the way Sentry aggregates errors over time I can see us never needing Sentry again.
- vanschelven 1y ago> notifications it's done: https://github.com/bugsink/bugsink/issues/3 https://github.com/bugsink/bugsink/issues/3