5 ms·

It'll be hard to position this against Sentry. Sentry's a joy to use and their performance product is so helpful in debugging performance issues

Lucasoato 2y ago
One of the Sentry inconvenience is self-hosting: it relies on so many services it can be very complicated to maintain.
- esafak 2y ago
  Does the self-hosted version have all the features?
  - easton 2y ago
    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)
    - whit537 2y ago
      We've started working on addressing this, fwiw: https://github.com/getsentry/team-ospo/issues/232 https://github.com/getsentry/team-ospo/issues/232
- mdaniel 2y ago
  I draw ones attention to the actual Open Source glitchtip which has a much more sane deployment, akin to the good old days of Sentry before they got Big Data-itis: https://gitlab.com/glitchtip/glitchtip-backend/-/blob/v4.0.8/docker-compose.yml https://gitlab.com/glitchtip/glitchtip-backend/-/blob/v4.0.8... (or its helm version, similarly not JFC https://gitlab.com/glitchtip/glitchtip-helm-chart/-/tree/61c97590fc761301279b12150a64c130e4627eb3 https://gitlab.com/glitchtip/glitchtip-helm-chart/-/tree/61c... )
  - threecheese 2y ago
    I’m not sure if you are responding to the wrong comment, or OP edited, but I am fascinated by what you posted and so can you explain a little bit?
    - mdaniel 2y ago
      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 Compare https://github.com/getsentry/self-hosted/blob/9.1.2/docker-compose.yml https://github.com/getsentry/self-hosted/blob/9.1.2/docker-c... with https://github.com/getsentry/self-hosted/blob/24.4.2/docker-compose.yml https://github.com/getsentry/self-hosted/blob/24.4.2/docker-... for what life used to be like for running Sentry on-prem. It was awesome 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
      - mdaniel 2y ago
        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
      - zeeg 2y ago
        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.

Lucasoato 2y ago

One of the Sentry inconvenience is self-hosting: it relies on so many services it can be very complicated to maintain.

esafak 2y ago
Does the self-hosted version have all the features?
- easton 2y ago
  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)
  - whit537 2y ago
    We've started working on addressing this, fwiw: https://github.com/getsentry/team-ospo/issues/232 https://github.com/getsentry/team-ospo/issues/232
mdaniel 2y ago
I draw ones attention to the actual Open Source glitchtip which has a much more sane deployment, akin to the good old days of Sentry before they got Big Data-itis: https://gitlab.com/glitchtip/glitchtip-backend/-/blob/v4.0.8/docker-compose.yml https://gitlab.com/glitchtip/glitchtip-backend/-/blob/v4.0.8... (or its helm version, similarly not JFC https://gitlab.com/glitchtip/glitchtip-helm-chart/-/tree/61c97590fc761301279b12150a64c130e4627eb3 https://gitlab.com/glitchtip/glitchtip-helm-chart/-/tree/61c... )
- threecheese 2y ago
  I’m not sure if you are responding to the wrong comment, or OP edited, but I am fascinated by what you posted and so can you explain a little bit?
  - mdaniel 2y ago
    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 Compare https://github.com/getsentry/self-hosted/blob/9.1.2/docker-compose.yml https://github.com/getsentry/self-hosted/blob/9.1.2/docker-c... with https://github.com/getsentry/self-hosted/blob/24.4.2/docker-compose.yml https://github.com/getsentry/self-hosted/blob/24.4.2/docker-... for what life used to be like for running Sentry on-prem. It was awesome 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
    - mdaniel 2y ago
      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
    - zeeg 2y ago
      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.