5 ms·
20B/month is interesting in the sense that Sentry should only be getting a transaction when there's an error in some third party application. Makes you wonder
by tyingq 9y ago
20B/month is interesting in the sense that Sentry should only be getting a transaction when there's an error in some third party application.
Makes you wonder if a couple of their clients paid for this error monitoring service, then quit watching it. That's a lot of errors.
- comboy 9y agoIf 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.
- xbzbanna 9y agoSuppose you track all client-side errors. Some portion of your users have a blocker that bans an analytics tool you use. Every hit generates an error. You could disable the error if you wanted in that case, but why not keep it online and use the graph on sentry to track how often it's happening?
- tyingq 9y agoAh, okay. Just seems wasteful to send the whole stack trace, local vars, etc, for that. But, yes, I can see people doing what you're describing.
- acdha 9y agoOne really big thing I learned from doing this on a public website: there are a ton of ISPs, browser extensions, antivirus and malware which inject really horrible JavaScript into every page. If you run Sentry as a front-end error collector you will get a ton of bizarre-seeming errors for other peoples’ code and, if you're really lucky, find that some of them used the same variable or function names as your code.
- brightball 9y agoIs there a good way of preventing unauthorized javascript injections? Some type of onReady cleanup script that can identify what is supposed to be there and then strip out everything else?
- jackweirdy 9y agoHTTPS
- brightball 9y agofacepalm
- tyingq 9y ago
- nitwit005 9y agoI'm sure that happens, but 20 billion a month is around 7700 requests per second, for presumably quite a few companies. It seems high, but not exaggeratedly so.
- huehehue 9y agoJust a few weeks ago, I hooked up Sentry to our co.'s client-side app, which is a widget/plugin of sorts that's installed on at least a few hundred thousand sites. Errors on even a tiny fraction of our users can be significant -- we immediately hit the free tier cap. 20B/month does not surprise me at all, especially considering some users are going to be overzealous in their event reporting.
- bentlegen 9y agoIf you have that kind of traffic, we recommend enabling sampling. All client libraries should support sampling out of the box.