Lighter weight replacements for Sentry bug logging
Lighter weight replacements for Sentry bug logging
I love Sentry, but it's very heavy. It runs close to 50 Docker containers, some of which use more than 1GB RAM each. I'm running it on a VPS with 10GB RAM and it barely fits on there. They used to say 8GB RAM is required but bumped it to 16GB RAM after I started using it.
It's built for large-scale deployments and has a nice scalable enterprise-ready design using things like Apache Kafka, but I just don't need that since all I'm using it for is tracking bugs in some relatively small C# and JavaScript projects, which may amount to a few hundred events per week if that. I don't use any of the fancier features in Sentry, like the live session recording / replay or the performance analytics.
I could move it to one of my 16GB or 24GB RAM systems, but instead I'm looking to evaluate some lighter-weight systems to replace it. What I need is:
- Support for C# and JavaScript, including mapping stack traces to original source code using debug symbols for C# and source maps for JavaScript.
- Ideally supports React component stack traces in JS.
- Automatically group the same bugs together, if multiple people hit the same issue
- See how many users are affected by a bug
- Ignore particular errors
- Mark a bug as "fixed in next release" and reopen it if it's logged again in a new release
- Associate bugs with GitHub issues
- Ideally supports login via OpenID Connect
Any suggestions?
Thanks!
You're viewing a single thread.
API compatible, but lower resource consumption - is missing some of the newer features (big one for me is tracing, but just install Tempo).
Not actually tried it, but looks promising
Thanks! I'll try it out. I don't see anything on their site about JavaScript source mapping, so I assume they don't do it. With Sentry, you upload the source map to the server as part of your JS build process, and their backend automatically maps minified stack traces to unminified ones using the uploaded source map. Maybe I'd be fine losing that in exchange for something lighter weight.
Hello, I'm the lead dev of GlitchTip. Fun to see it mentioned here. Source maps are supported. I wish I had time to make the feature easier to use and write better docs. Contributions are welcome. It's very much a hobby project for the little time I have after work and family. Right now all of my attention is on an event ingest rewrite to work with fewer resources.
Nice to see you on here! I understand the lack of time - I've got some projects I've had on hold for years because of time constraints. I'm definitely going to try Glitchtip.
If I get some free time, I'll see if I can write some docs about using source maps for JS apps. Sounds like it works in the same way as Sentry's does.
It was a great idea for GlitchTip to reuse the Sentry SDKs and CLI, because their SDKs are solid. They've got the best .NET SDK out of all of the error logging systems I evaluated two years ago which is why I was using Sentry. Unfortunately, Sentry has become significantly heavier over those two years.
https://glitchtip.com/blog/2022-04-25-glitchtip-1-12
This blog post mentions that it should be possible at least!
Im currently using their free tier for a hobby project and have been happy with it. Have considered moving over to self hosting the solution, but have been keeping off on it due to resource contraints, but might make the leap soon! Would be nice to get use of the uptime pings, which currently would fill the event way too quickly for the free tier.
Perfect, thanks. Strange that it's not in their docs, but it does seem like their docs are very minimal.