Pain point · Self-hosting & upgrades · Blocks work
Self-hosted Sentry runs around 70 containers, hard to debug
4 source threads · first seen 2025-04 · last seen 2026-08
Summary
A self-hosted Sentry deployment requires dozens of containers for what should be one piece of software, making debugging hard and annoying.
- Affects
- Sysadmin running self-hosted Sentry via Ansible
- Workaround
- Throws logs at an LLM to help debug.
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“20 different components like Sentry self-hosted versions do”
“for some reason they think that having 70 containers running for what should amount to one piece of software is okay”
“like a self-hosted Sentry install, just look at all of the services”
“I still love Sentry, but it’s so enormous now that it isn’t practical to self-host for smaller businesses”