[nimih]

Sentry is technically self-hostable, but they provide no deployment guidance beyond running the giant blob of services/microservices (including instances of postgres, redis, memcache, clickhouse, and kafka) as a single docker-compose thing. I get why they do this and think it's totally reasonable of them, but Sentry is a very complicated piece of software and takes substantially more work IME to both get up and running and maintain compared to other open-source self-hosted observability/monitoring/telemetry software I've had the pleasure of working with.

[miohtama]

Our Linux devops engineer, who had not used Sentry before, set up a self-hosted Sentry in a day.

[chipdart]

> Our Linux devops engineer, who had not used Sentry before, set up a self-hosted Sentry in a day.

I've also spent 1 hour setting up a Kubernetes cluster on a set of desktops I had lying around. This does not mean Kubernetes is simple or easy.

[merb]

It’s easy to setup but painful to keep running and it’s hard to backup.

[tapoxi]

Yeah, it works for a time, but they don't support on-premise versions and they don't offer a Helm chart install, its all community based.

I tried it for well over a year, and there are so many moving parts and so many "best guesses" from the community that we had to rip it out. There's a lot of components, sentry, sentry-relay, snuba, celery, redis, clickhouse, zookeeper (for clickhouse), kafka, zookeeper (for kafka), maybe even elasticsearch for good measure. It did work for a time, but there are so many moving parts that required care and feeding it would inevitably break down at some point.

Problem is I can't ship data to their SaaS version because we have PHI and our contracts forbid it, even if scrubbed, so I had to settle on OTEL.

[tnolet]

Day 1 vs day 2. That’s why the SaaS version exists.