Closed
Bug 1464138
Opened 6 years ago
Closed 6 years ago
Browser Error Reports are getting ratelimited
Categories
(Firefox :: General, enhancement, P3)
Firefox
General
Tracking
()
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
firefox62 | --- | affected |
People
(Reporter: osmose, Assigned: osmose)
References
Details
When sending an error report to Sentry for the Firefox JS Error project, I'm receiving a "429 Too many requests" response from the nginx sitting in front of it.
I asked wezhou last week what the stats were for nginx rate-limiting incoming errors for the project:
> total requests for today: 1455004, rate limited: 1448907
That's over 99.5% of errors being rate-limited. The current limit is set to 30 errors per-minute.
We should bump that rate limit up a bit, but a large amount of those errors are not immediately useful to us as well:
- We do no client-side filtering of errors caused by add-ons.
- We send errors from out-of-date Nightlies that don't have fixes that have already landed.
- We send errors for known issues that have a large amount of entries in Sentry already; collecting more data for these issues isn't terribly useful for us.
The goal of this bug is to get our error-sending rate to a point where the rate limit isn't constantly being hit.
Comment 1•6 years ago
|
||
[Triage driveby: sounds like this is being worked on in dep bugs, so calling this P3]
Priority: -- → P3
Assignee | ||
Comment 2•6 years ago
|
||
JavaScript error collection is being shut down and has already been removed from Nightly, so this isn't relevant anymore.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•