Sentry is self hostable. https://develop.sentry.dev/self-hosted/

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.

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

> 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.

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

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.

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

PostHog and Rudderstack say the same things. They're not really self hosted. But that's the rub, if someone authored a good operator for Sentry, Sentry as a commercial service would cease to exist. That's not good in my opinion, they do real innovative stuff.

It's tough. We should have never done "give away the software, charge for hosting." The market, in every sense, has been telling you that you're really building value for AWS, for years, by doing that.

But not foss. It's using the BSL or FSL or whatever.

Although I do not like those licences, I would not care so much about 2yrs until it goes FOSS. Before all this rush development RRDTool and OpenTSDB was so slow, this whole thing seems rather ideological than substantial criticism. Now going down the licence rabbit hole based to criticise the original argument seems like a classical strawman.

Just want to say I appreciate your stance.

(also no one should feel like they have to contribute to our SDKs, but please file a ticket if somethings fucked up and we'll deal w/ it)

I was supporting a variation in my head of the "Yeah but who wants to contribute to an SDK for a service that you need to pay for?" claim.

You can self-host for free, so maybe @hahn-kev don't mind contributing to the SDK now.

For me, I refuse to contribute to an open-source SDK for a non-foss product. And I refuse to self-host a non-foss product.

Personally, I don't care if non-foss licenses speeds development. So yeah in my case it's ideological.

https://glitchtip.com/ is an Open Source form of Sentry created after they went closed source, if you are interested in something like that.

If I'm using something for employment, and the employer would get value out of it getting a bug fixed, why would I not fix it?

Sentry provides a great hosted service. You can self host if you like, but it’s nicer to let them do it