Selfhosted

39927 readers

407 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

Lighter weight replacements for Sentry bug logging (upvote.au)

submitted 9 months ago* (last edited 9 months ago) by [email protected] to c/selfhosted

6 comments fedilink hide all child comments

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 are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 9 months ago

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.