Issue
Data is being scrubbed and I do not know why. I want to know the exact rule that is scrubbing my data so I can have finer control over the scrubbing rules without disabling Data Scrubbing completely. There are no modifications of the event on the client, and yet in Sentry, there are fields being shown as [Filtered].
Sentry will scrub events automatically based on key names and the values. When Sentry detects a value or key name that is often considered sensitive or may possibly contain PII we replace the value with [Filtered]. We scan through the fields listed here of the event payload sent to us on ingest.
Applies To
- All Plans
- Self-hosted
Symptoms
- I have fields being scrubbed, but they do not contain PII
Resolution
When an event has gone through one of the default scrubbing rules server side, we output the reason in the JSON view of the event. From the event view, click on the
{ } button to view the raw JSON of the event. Under the _meta tag will list all the fields that have gone through scrubbing with a reason.For example, when a field has been scrubbed via our default Auth scrubbing, there will be an outcome of
@password. Similarly, if the value is scrubbed because our regex detected the value was a credit card number, there will be an outcome of @creditcard.If the outcome listed in the JSON view is
strip-fields, that means the data was scrubbed because it was either a match, or partial match, to something that was added to the Global Sensitive Fields option at the org level, or Additional Sensitive Fields at the project level.