GlitchTip 3.3.0: Feedback survey, uptime port monitoring, issue fingerprint grouping

https://lemm.ee/post/1370076

GlitchTip 3.3.0: Feedback survey, uptime port monitoring, issue fingerprint grouping - lemm.ee

I’m the lead developer of GlitchTip, an open source error and uptime monitoring platform. This release includes port monitoring for internal assets like PostgreSQL. GlitchTip aims to be easy to self-host. We’re compatible with Sentry SDKs. If you’ve found Sentry’s backend too complex to run or prefer 100% open source code [https://gitlab.com/glitchtip/], give GlitchTip a try. We’re always looking for Python, Rust, and TypeScript contributors. I’m happy to answer any questions.

I installed it with Ansible a few months ago and it’s been solid. It’s really nice to see bug reports with so much detail.

At the same time I also connected my dev environment to it, and it’ s been helpful for webdev getting errors from both front- and backend in the same interface when adding features.

For dev it’s less useful to have the history saved, so I think a standalone binary without setup that’ll simply accept anything and keep in memory would be useful for a small audience.

I’m glad it’s helpful to you. I was toying with the idea of converting the backend to Rust. It’s easier to write async Rust than Python. I believe that would allow me to distribute a small all-in-one binary - except for Redis and PostgreSQL. I have entertained the idea of making Redis optional. In trivial cases, it’s possible to abstract a database ORM and use something like sqlite. But I don’t think this would happen for GlitchTip. I’m currently using PostgreSQL specific features like jsonb. Of course contributions are welcome and with enough effort anything is possible.
David Burke / learn-rust · GitLab

GitLab.com

GitLab