GlitchTip 3.3.0: Feedback survey, uptime port monitoring, issue fingerprint grouping
GlitchTip 3.3.0: Feedback survey, uptime port monitoring, issue fingerprint grouping
GlitchTip 3.2.0 adds refinements for uptime monitoring and issue grouping. We also have a new user feedback survey.
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, 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.
Yeah, pgsql and redis are probably to much to work around, and the market too small. For those it could be useful they probably already have an installation on a server that can be used.
For my usage it's perfectly fine running in python, so far not many daily users and not many bugs - most days nothing is reported. If I had more users or with performance telemetry enabled I might want rust. Better for the environment and I could run it on a smaller instance. That said, I believe GlitchTip is already ahead of Sentry in resource usage - I didn't install Sentry, but I saw all the systems needed and that was the main reason for going with GlitchTip. I'm mostly OK with their license.