3 ms·
If you deploy some non-edge-case bug then you can easily generate thousands of events before you even receive the notification - assuming your service is any po
by comboy 9y ago
If you deploy some non-edge-case bug then you can easily generate thousands of events before you even receive the notification - assuming your service is any popular, but even if it's not it can be e.g. some stuck background job.
Btw, it's on average 7.5k events per second. Not that drastic but of course peak, not average is what matters.
- tyingq 9y agoI get the idea, but I would think the right use of the product is to fix the root causes, or suppress errors that aren't actionable. I was basing this off of somewhere on the site that mentioned roughly 200 companies using it. Perhaps it's grown. Would be interesting to know the total per month after they are deduplicated.
- zeeg 9y agoNot sure where you'd see 200 companies (we've had more than that for most of Sentry's lifetime). Not every team lines up to a company, but napkin math I'd say we have 10k - 20k companies using our cloud service. That's also excluding all of the open source installations, which is a pretty large number.
- the_mitsuhiko 9y agodisclaimer: Armin from Sentry here I'm not super happy that this number is in the title because I find this number myself very irrelevant to our operations (not even sure this number is correct, it sounds too small). What's more challenging to us is the complexity of individual events and the bursting of it. A lot of interesting engineering went into that.
- dalore 9y agoYeah we use sentry, and quite often generate an insane amount of errors on occaison (sorry). And also management not prioritising fixing low priority errors, means we have quite a high error count even then. That 20b does sound quite low based on just our usage of it.