Re:Sentry.io outage
by np_tedious on Friday May 06, 2022 @10:42AM
(#31285714)
I kind of agree. Their source map thing to get better traces is a nicety, but few would find it release blocking to forgo it
Edit due to other comment: this assumes CI/CD. If you were deploying only weekly then this might be good reason to delay
It can be desired to continue on failure, the tradeoff is that there is then a release out there with lacking error-sourcecode mapping.
I think if your release cycle is longer, then you will prefer not to deploy without sourcemaps.
I prefer a 98% accurate error reporting better than a 100% one I can't push to production.
Or maybe I'm not understanding well the value Sentry offers, of course.