sentry

Sentry is indeed, and is open source and self-hostable: https://github.com/getsentry/sentry It’s a pretty large app (I think >1M lines of Python). I ran a self hosted version for several years and found it performant and pretty easy to keep running and updated.

I don't believe it's a fork, but https://gitlab.com/glitchtip/glitchtip-backend is MIT and aims to be the actual Open Source replacement for Sentry Given that it's almost been 2 years since the FSL change[1], I would imagine it's possible to set up a rolling mirror into https://gitlab.com/glitchtip/sentry-open-source/sentry that serves as an easier "what is actually open right now?" browser. I just realized while typing that out: a snapshot of the source code actually doesn't help anyone know if a particular commit is Apache 2 since the change is dependent upon an accounting record on GitHub That was the advantage of the BuSL 1.1 scheme, that those cut-over dates were embedded in the file https://github.com/getsentry/sentry/blob/22.7.0/LICENSE#L19 and https://github.com/getsentry/sentry/blob/22.8.0/LICENSE#L19 is open in 10 days 1: https:

Not as the creator intended, but Commit signing on GitHub is mostly an automatic thing at this point if you use pull requests and squash merges. The commits on the PR itself are unsigned, but the merge to the branch is attested and marked as signed by GitHub itself. Since you need to have permission at the time of merge, it's a rather trustworthy indication. Here an example from Sentry's master which other than bot triggered reverts are all verified: https://github.com/getsentry/sentry/commits/master/

Late to the party here but we (Sentry) have been using ECharts since 2018 (https://github.com/getsentry/sentry/pull/9072) and still holding strong!

Likely only a handful of people care, but Sentry hasn't been open source in quite a while https://github.com/getsentry/sentry/blob/24.12.1/LICENSE.md (I'd have to do tag-spelunking to find the last Apache 2 version) Glitchtip is the Sentry compatible open source (MIT) one https://gitlab.com/glitchtip/glitchtip-backend/-/blob/v4.2.2... with the extra advantage that it doesn't require like 12 containers to deploy (e.g. https://github.com/getsentry/self-hosted/blob/24.12.1/docker... )

This is a great initiative, but one wonders to which degree this is mostly a marketing stunt, white-washing their own "fair source" efforts. Sentry is a multi-billion company, and Open Source pays exactly none of their bills (though it may serve other purposes). This leads to pages such as [1] where they actively steer users away from self-hosting their "open source" (in name only) solution. Much has been said about Sentry's switch to "Fair Source"[2], but for me personally, the ship of "open source in name only" sailed long before that with the ever-increasing complexity of managing your own setup.[3] It’s clear that the priority here has shifted to pushing users toward their hosted, paid plans. Business models beat licenses every time if you want to understand actual intentions. Disclaimer: I am the solo-everything at a competitor, whic

> Sentry has never been GPL. That was my mistake, my brain remembering wrong. https://github.com/getsentry/sentry/blob/9.1.2/LICENSE was its last open source license, MITish, right? As for calling it "*source" and saying "oh we're not pretending its open source"? This is a point of opinion, but I think that's disingenuous marketing, at best.

1) Do you have two separate codebases for free and paid? No. Sentry has one codebase between free and paid. We have a Django monolith plus some services where all our features are implemented: https://github.com/getsentry/sentry https://github.com/getsentry/relay https://github.com/getsentry/snuba https://github.com/getsentry/vroom etc. We have a Docker Compose wrapper in a separate repo: https://github.com/getsentry/self-hosted We have a private repo called getsentry/getsentry that is another Django app that imports the public one and uses Django signals (iirc) to meter usage for billing. That is what we deploy to SaaS. All product features are implemented in the public repos. 3) How about employee access? Employee access is managed through UI, I honestly don't know whether it lives in getsentry/sentry (public) or getsentry/getsentry (pr

Sentry is built on-top of Django. It's a good example of a real-world non-trivial code base that has had to adapt as it grew up and scaled up. I haven't looked at the code in a few years, but I used to run it on-premise and found it fairly approachable and well-written, but with just the sorts of hacks you'd expect to see in a software code base that had evolved over time. https://github.com/getsentry/sentry Here's all the database models: https://github.com/getsentry/sentry/tree/master/src/sentry/m... Here's an example of hacks in the form of massive caching to improve performance: https://github.com/getsentry/sentry/blob/master/src/sentry/d...

Sentry produces nothing of value? You don't value an open source error tracking and performance monitoring platform? https://github.com/getsentry/sentry

> You invent something, and then immediately turn it into a cheap commodity by releasing it for free. Exactly. A 71-line python script https://github.com/getsentry/sentry/commit/3c2e87573d3bd16f6... was groundbreaking when it came out and the fact that it springboarded into a startup is commendable. But 15 years later and Functional Software Inc. d/b/a Sentry has to support 100+ (according to their marketing material) platforms as well as adding new verticals in UX session replay, web performance, backend profiling, CORS error monitoring, code coverage etc. just to keep the growth machine going. That's not OSS' fault.

https://github.com/getsentry/sentry/pull/60144 -> https://github.com/getsentry/sentry/blob/d4d89e2fa93ad99f13d... If they're going to all this trouble for "ambiguity," I don't know why they wouldn't further extend their custom SPDX identifier to include the "2 year" rollover, since that's one of their pearl-clutching reasons for this bullshit: https://github.com/getsentry/loose-confederation/issues/4

It's source available under the BSL: https://github.com/getsentry/sentry. After four years it becomes open source (probably to prevent "AWS Elastic Error Handling service(tm)" from becoming a thing) You can still run it for your company for free, if you feel like managing all of the infra it requires.

Sentry: https://github.com/getsentry/sentry