Closed Bug 1509891 Opened 6 years ago Closed 5 years ago

Remove Sentry projects for Browser Error Collection

Categories

(Cloud Services :: Operations: Miscellaneous, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: osmose, Assigned: brian)

References

Details

We're winding down the prototype browser error collection project. Once the client side code is removed (bug 1509888) and sent out to most Nightly users, we can remove the project entry on Sentry.

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.

Blocks: 1426479

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.

Flags: needinfo?(wezhou)

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!

Flags: needinfo?(wezhou)

I've gone ahead and deleted the nightly-js-errors project on Sentry.

Assignee: nobody → bpitts

This can be closed. Rate limit rules was removed before.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.