Our headline feature for GlitchTip 5.2 is a design refresh, based on the Material Design 3 system. A new graph on the issues list page allows you to see recent trends of events in the past 24 hours or two weeks. Dark mode has been improved as well.
GlitchTip 5.2 includes a denial of service (DOS) vulnerability fix from the brotli project. GlitchTip already mitigated the memory consumption partially, capping impact at around 1GB ram per request. The latest version of brotli allows us to lower this further. We recommend all users concerned about DOS attacks, to upgrade soon.
GlitchTip 5.2 has experimental support for PostgreSQL as our only database. Valkey (or Redis) are no longer required. If you set VALKEY_URL to an empty string, GlitchTip will now utilize Postgres for cache, celery, and sessions. This requires less ram, but yields slower performance.
Our existing (experimental) bin/start-all-in-one.sh script has been updated to support scaling. Previously, running more than one instance would start multiple celery beat schedulers. This has been improved to start just one. Without Valkey, you can now run GlitchTip on as low as 256mb ram. We recommend this only for the most shoe-string of budgets. Larger instances should not use the all-in-one instance.
Adventurous users should try this out and report any issues on GitLab. With Docker Compose, you can set the command to bin/start-all-in-one.sh and remove the worker/beat services.
Our settings have also been slightly simplified. DISABLE_SERVER_SIDE_CURSORS now defaults to False, as this setting leads to errors when using more than one app server. Over time, we are moving to a model where more settings have "just works" defaults, but can still be overwritten by advanced users. We don't intend any of these changes to be breaking, but if you do have a problem, then please open a GitLab issue.
Finally our design refresh uses slightly LESS JavaScript.
GitHub user vltansky let us know about GlitchTip MCP, used for connecting with AI models in the standardized MCP convention. The GlitchTip team remains firmly committed to our open-source, no-bloat, no-forced-AI philosophy, ensuring user data is never sent to third parties for model training or usage. Opting into communicating with these models is well within our scope. We would consider a contribution to add MCP support directly to GlitchTip using Python, so long as it's disabled by default. Please note that glitchtip-mcp is not affiliated with the core GlitchTip team.
GitLab user tytan652 contributed a highly requested feature to control social authentication registration. ENABLE_SOCIAL_APPS_USER_REGISTRATION can now be set independently of ENABLE_USER_REGISTRATION. This allows users to enabled authentication using only single sign on.
GitLab user vanschelven, from Bugsink, notified us of a new DOS mitigation in brotli. Our Renovate bot updated brotli and core contributor bufke applied the fix. Our existing mitigation already limited memory usage to under 1GB, but this patch greatly improves it. Users concerned about DOS attacks should upgrade as soon as possible. Read me about the brotli DOS vulnerability and mitigation here.
See a full list of contributors on our GlitchTip group on GitLab. Thank you to all contributors, especially those making the more important and less headline worthy changes that make GlitchTip better!
Bitnami, in the past, has offered free helm charts for many popular projects including Postgres and Valkey. They have since abandoned these offerings. Our 6.0 release of glitchtip-helm-chart introduces breaking changes to replace Postgres and Valkey charts with alternatives.
GlitchTip search will soon support * wildcards thanks to a combination of trigram index + tsvector based full text search.
We're working to improve our Python asyncio support to process more requests with less system resources. django-valkey supports async cache. django-async-backend introduces async for raw SQL connections in Django. These packages will require time to stabilize. In the future, we plan to default to an async python web server. However at this time, performance is not yet acceptable for larger deployments due to lack of async support in Django cache and ORM.
We'll continue refining our new design. We hope to add a high-contract theme and better dashboards.
Our glitchtip.com website needs updated to incorporate the new design. We're aiming to emphasize the many deployment options users have, including our own EU server and partner organizations that host and share revenue with GlitchTip. Freedom to choose is a core value of the GlitchTip team.
Your time and financial donations are the only thing that keeps GlitchTip development going. GlitchTip is not backed by venture capital.