A person who was laid off said it was supposed to be Wednesday but HR flubbed the e-mail timing. Presumably once the e-mail went out, they were like “well, guess we might as well make it effective now instead of in 2 days…”
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.
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.
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.
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.
I've been using GlitchTip https://glitchtip.com with the Sentry SDKs and I couldn't be happier. Completely self-hosted, literally just the container and a db, requires zero attention.
GlitchTip is very simplistic and miles away from Sentry.
We really wanted to keep using it, since it was easy to selfhost, but the UI was not giving enough information from a dev perspective to be very useful : grouping, filtering and labeling issues is very basic, which prevents understanding.
We decided to self host sentry, which is an absolute beast to deploy, the open-source helm chart is nowhere near production level, and the underlying technologies are quite hard to maintain (Kafka, zookeeper, clickhouse...). We had to work on it constantly for two months to stabilize it, and now fear the moment we'll want to update. The dev teams love it, so it was worth the hassle!
This is something we're (Sentry) not happy about. Always hard to maintain the simplicity with growing product functionality. There's efforts underway (e.g. https://github.com/getsentry/self-hosted/issues/1763) to reduce the footprint if you only need portions of the functionality.
I was responding to the One of the Sentry inconvenience is self-hosting: it relies on so many services it can be very complicated to maintain part, and also reminding readers that if they, too, hate companies that rug-pull their open source licenses, there is a band-aid for both parts
It would take a ton of work to dig up the actual memory and CPU requirements of each one, but rest assured they're not zero, so every one of those services eats ram and requires TLC when, not if, they shit themselves. So, more parts == more headaches with all other things being equal
Then, I deeply appreciate that there are a whole spectrum of reactions to the various licensing schemes in use nowadays, and a bunch of folks don't care. I care, though, because I have gotten immense value from open source projects, and have contributed changes back to quite a few. It has been my life experience that many of those "source available" licenses usually are very hostile toward making local real builds and if I can't build it to match how prod goes, then I can't test my fixes in my environment and then I can't contribute the PR with any faith
Where was the rug pull? The only people negatively impacted by Sentry's relicensing were people trying to monetize it. Did we negatively impact you? Anyone else in the community? Not that I've ever seen evidence of.
Live and die on your hill. We'll keep focusing on building our product - which requires us to be able to be able to pay developers for the enormous amount of time it takes them.
I ordinarily would have just ignored your troll comment, but this was so incredibly short sighted that you were obviously wanting some sparks so now you'll get them. Sentry didn't start life with a source available license, even though the threat model to the business was exactly the same at that time: the cloud for sure existed, I know because I ran Sentry self-hosted upon it. And your cited enormous amount of time and money to pay developers didn't spontaneously spring into being 6 months ago, either. So, the tone that was set was that Sentry was open source with all the rights and privileges that came with it. Until someone got butthurt and decided they needed not just one source available license but then their own source available license just to ensure lawyers never go hungry
> Live and die on your hill.
You, too. Enjoy your mansions and yachts from all the ontold riches that your new licensing scheme will surely bring you in exchange for lighting fire to any trust gained
The challenge with making statements like this is you're making them against not only the person who made the decisions, but also the person who holds 100% of the facts, and will openly share them.
So lets talk about the facts, because the paint a pretty clear narrative, rather tha one that people would prefer to believe.
1. I built most of Sentry (back then), and while we had a few contributions here and there, it was almost exclusively my time, or future employees times. So no community contribution concerns.
2. We relicensed because of a new threat, not one that existed 16 years ago when I started the project. That threat was GitLab, who was openly trying to commercialize Sentry. They never once contributed to the project, nor did they want to contribute back as part of that strategy. I know this to be true because I asked them to.
3. We built the FSL because the BUSL did not create a strong enough conviction to our values - of which we repeatedly have put words into action on. We wanted to cement those values, and make it easier for people who had our same concerns, but also wanted to create more open source, to be able to achieve that _without_ undue risk or legal fees.
There is a huge difference in the way Sentry operates, and the way some of these other organizations have chosen to relicense (or in some cases, legitimately rug pull).
So you can say what you will, but we've always been straight forward with our beliefs, and talk about these things publicly all the time. I'm not here to convince you of changing your beliefs, but I will never sit idly when people spread false information, especially about us.
I'm also going to enjoy some popcorn when they don't upgrade their redis image past 7.2.4 due to the "AWS^H^H^HSentry gonna steal our shit" license change. Turns out, everyone taking their ball and going home doesn't make for a collaborative environment -- who could have foreseen?!11
yes, every feature (but billing, iirc) is in self hosted. which means you need all of their backend dependencies (kafka, zookeeper, other things that are probably easier to manage than those two)
I like that polar supports funding specific issues or pull requests. Seems like a nice way to help fund a project while also helping prioritize issues you care about.
Thank you! Important callout: We designed issue funding for maintainers & contributors vs. bounty hunters. We don't believe in traditional bounties. More on this here: https://polar.sh/polarsource/posts/introducing-rewards
Its been a few years since I've had to go through Penn Station directly other than for LIRR. As I recall from my NE Corridor commuting days the lounge requires an Amtrak ticket. The NJ Transit waiting area had no lounge and no seats meaning people would begin to bunch up on the stairs. Admittedly, it might have changed in the intervening years.
