Remove Sentry projects for Browser Error Collection
Categories
(Cloud Services :: Operations: Miscellaneous, task)
Tracking
(Not tracked)
People
(Reporter: osmose, Assigned: brian)
References
Details
Reporter | ||
Comment 1•6 years ago
|
||
The client side code has been removed; I'm gonna let that sit in Nightly for the rest of the week, and next week we can check the number of incoming errors and test what happens to old clients when the service stops accepting errors from them before cleaning up the data.
Reporter | ||
Comment 2•6 years ago
|
||
I've checked and the code handles an invalid/missing project gracefully, so we're good to delete the project and associated rate limiting rules.
wezhou: I have access to a delete project button, should I just do that? I don't have access to remove the rate limiting rules though.
Hi Michael,
Is it the "nightly-js-errors" project under "firefox-js-errors" team? If so, feel free to delete it at your convenience. I'll remove the rate limiting rules afterwards.
Let me know if there are issues.
Thanks!
Reporter | ||
Comment 4•6 years ago
|
||
I've gone ahead and deleted the nightly-js-errors project on Sentry.
Updated•5 years ago
|
This can be closed. Rate limit rules was removed before.
Description
•