implement sensitive data scrubbing for sentry (socorro)
Categories
(Socorro :: General, task, P2)
Tracking
(Not tracked)
People
(Reporter: willkg, Assigned: willkg)
References
Details
Attachments
(5 files)
We updated to sentry-sdk. Now that we're using that, we need to make sure we're not sending PII along with Sentry error reports.
The Socorro webapp has some sanitizing code. I think we can generalize that, combine it with the code in socorro/lib/sentry_client.py
so we have a single module that we use for setting Sentry up, sanitizing events, and providing some other functionality.
Assignee | ||
Comment 1•3 years ago
|
||
Grabbing this because it's blocking the migration.
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 2•2 years ago
|
||
I did a lot of the R&D work in bug #1764569.
There's a Sentry migration doc that contains analysis on what we need to scrub and how here:
We're going to use the newly developed Fillmore library (https://pypi.org/project/fillmore/) to scrub Sentry events.
Assignee | ||
Comment 3•2 years ago
|
||
Assignee | ||
Comment 4•2 years ago
|
||
Assignee | ||
Comment 5•2 years ago
•
|
||
This adds two new metrics we need to add to the dashboard:
webapp.crashstats.apps.sentry_scrub_error
processor.sentry_scrub_error
These aren't prefixed with "socorro". Maybe when we move to GCP we can fix that.
Assignee | ||
Comment 6•2 years ago
|
||
Assignee | ||
Comment 7•2 years ago
|
||
Assignee | ||
Comment 8•2 years ago
|
||
Assignee | ||
Comment 9•2 years ago
|
||
Assignee | ||
Comment 10•2 years ago
|
||
Assignee | ||
Comment 11•2 years ago
|
||
Assignee | ||
Comment 12•2 years ago
|
||
Assignee | ||
Comment 13•2 years ago
|
||
Assignee | ||
Comment 14•2 years ago
|
||
I deployed this in bug #1782791 just now. I checked Grafana and Sentry and everything looks ok. Any new issues, we'll do new bugs. Marking as FIXED.
Description
•