Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Sentry.io outage

status.sentry.io

Post reply on HN
Print view View original

21–30 of 84 posts

Re: Sentry.io outage

#21

Post by heipei »

Klathmon wrote: post #7
dijit wrote: post #6

Sentry is a great product, I love even more that you can self-host it; otherwise I would be one of the people denigrating everyone for running their entire operation on SaaS products. As it stands if their reliability leaves something to be desired: run your own. These things happen, they’re more common the more complicated or huge your setup. Good luck to them in getting it resolved.

Has anyone here used their self hosted version? I always assume that running an on-prem version of a SAAS offering is going to be a shit show, but I'm curious if anyone here uses it?

I am using it, but it is not fun to use. It spawns 28 Docker containers (yes, that's the actual number), including things like nginx, postgres, memcached, redis, kafka, zookeeper, clickhouse. I've tried upgrading it once and it failed miserably, after which I simply started from scratch.

I would like to use their hosted version, or a more stable paid on-prem version. Pricing is not the issue for me, but I don't want to introduce another third-party service and have to include that in compliance documentation for our customers. That is the reason I still self-host many things to be honest.

Re: Sentry.io outage

#22

Post by rtpg »

bovermyer wrote: post #4
orose_ wrote: post #2

It's somewhat ironic that a monitoring service has shit the bed. For some reason at work we're using Webpack, and, for some reason we are also using Sentry Webpack plugin that is causing our whole CI to fail. This is fine.

Maybe it's just me, but I feel like monitoring software failures should not cause application failures.

It’s likely that the failure is around Sentry’s “signal a release and upload your source code out of band to us” feature.

In theory things shouldn’t break but if your CI process involves signaling a third party, it can fail from that (hopefully you can temporarily disable it or something of the sort)

Re: Sentry.io outage

#23

Post by misnome »

viraptor wrote: post #20
Cthulhu_ wrote: post #15

Earlier quoted context omitted.

> run your own. Is there a good name for this theory that self-hosting something is more reliable? I mean yeah, if you have an outage it only affects you and your customers so I guess it's an improvement in that regard, but thinking you're better at running software than a SaaS is hubris.

Not sure about the name, but there are reasons to expect more reliability. You're only handling your traffic, not all the customers at once. You don't need to scale/distribute that far. And you can predict the traffic/storage needs better. In SaaS case someone does it for you, but it's a much bigger problem and they care less about you (as a single customer id 37826) than you do.

And you can either stick with the same version/featureset, or time upgrade outages to periods when you know your operations won’t be impacted.

Re: Sentry.io outage

#27

Post by Nextgrid »

Cthulhu_ wrote: post #15
dijit wrote: post #6

Sentry is a great product, I love even more that you can self-host it; otherwise I would be one of the people denigrating everyone for running their entire operation on SaaS products. As it stands if their reliability leaves something to be desired: run your own. These things happen, they’re more common the more complicated or huge your setup. Good luck to them in getting it resolved.

> run your own. Is there a good name for this theory that self-hosting something is more reliable? I mean yeah, if you have an outage it only affects you and your customers so I guess it's an improvement in that regard, but thinking you're better at running software than a SaaS is hubris.

> but thinking you're better at running software than a SaaS is hubris.

Disagreed on several points.

First off, if you're using something like Sentry, chances are that building and running software is your job so it should not be a problem. If self-hosting Sentry is a problem I would start doubting the skills of your tech team.

Second, running a service for your own use is very different to running a service that has to scale to the entire world. Your service won't need as many moving & distributed parts as the SaaS Sentry since it will only ever have to handle a fraction of the latter's traffic.

Finally, if you're in control, you can schedule risky maintenance operations during times where a potential accident (operator error, etc) won't affect your business. You can't do that with an SaaS.

Re: Sentry.io outage

#28

Post by the_gipsy »

rtpg wrote: post #22
bovermyer wrote: post #4

Earlier quoted context omitted.

Maybe it's just me, but I feel like monitoring software failures should not cause application failures.

It’s likely that the failure is around Sentry’s “signal a release and upload your source code out of band to us” feature. In theory things shouldn’t break but if your CI process involves signaling a third party, it can fail from that (hopefully you can temporarily disable it or something of the sort)

Yes the CI should fail, or else you would be deploying something that can't match your errors to your source code (via the sourcemaps which is what presumably gets uploaded to sentry on the CI run).

Re: Sentry.io outage

#29

Post by that_guy_iain »

nicoburns wrote: post #5

Obviously it's never good when a service has an outage, but it looks like Sentry's status page reports the actual status which makes a nice change.

Plus, it's literally the first time I've seen them having an outage over the years so it seems like they're generally doing well on staying up.

Re: Sentry.io outage

#30

Post by joekrill »

Klathmon wrote: post #7
dijit wrote: post #6

Sentry is a great product, I love even more that you can self-host it; otherwise I would be one of the people denigrating everyone for running their entire operation on SaaS products. As it stands if their reliability leaves something to be desired: run your own. These things happen, they’re more common the more complicated or huge your setup. Good luck to them in getting it resolved.

Has anyone here used their self hosted version? I always assume that running an on-prem version of a SAAS offering is going to be a shit show, but I'm curious if anyone here uses it?

I looked into it at one point and found it required a lot of underlying services and seemed really complex. Primarily I was worried about the maintenance costs moving forward with something like that.

There is an open-sourced option called GlitchTip (https://glitchtip.com/) that is much simpler to self-host. I believe they forked the Sentry repo before the license change. It's not quite as feature rich but is a pretty great alternative.

Post reply on HN