Logging feature scrubs data event with all data scrubbing options turned off

[lilac swallow]

I am using the new logs feature. Even with all data scrubbing options turned off for my org and project, I see [Filtered] for many logs. How can I disable this?

[graceful frost]

Hi @lilac swallow. I'm happy to dig into this for you! I'll check my internal sources for answers to your question! :wave:

---

If you are seeing [Filtered] in your logs even after disabling all data scrubbing options at both the organization and project levels, this is a known point of confusion and frustration for some Sentry users.

Here’s what the knowledge sources confirm:

• Sentry applies data scrubbing by default to protect sensitive information. This includes both key names and values that match certain patterns (like "password", "token", "auth", etc.) or are listed in the sensitive fields configuration. This scrubbing can be controlled at both the organization and project level, and there are toggles for "Data Scrubber" and "Use Default Scrubbers" in the Security & Privacy settings. If both are disabled, in theory, no scrubbing should occur, and you should not see [Filtered] in your logs or events. However, some users have reported that scrubbing still occurs for certain fields even after disabling all options, and that it may take some time (20–30 minutes) for the settings to propagate fully after changes are made Why am I seeing "[Filtered]" in my event data? Fields are being data-scrubbed ([Filtered]) which I am unable to debug and redact myself.

• If you are still seeing [Filtered] after disabling all scrubbing, it is possible that:

  • There is a delay in the propagation of your settings.
  • Organization-level settings are overriding project-level settings.
  • There is a bug or undocumented behavior in the ingestion pipeline, especially for new features like Logs.

• You can check the exact reason why a field was scrubbed by viewing the event’s raw JSON in Sentry (click the { } button in the event view). The _meta section will show the scrubbing rule that was applied (e.g., @password:filter for default rules, or strip-fields for custom sensitive fields). This can help you determine if the scrubbing is coming from a default rule, a custom rule, or something else How do I find out exactly what is scrubbing my data? Fields are being data-scrubbed ([Filtered]) which I am unable to debug and redact myself.

• If you have confirmed that all scrubbing is disabled and the problem persists, this may be a bug or an edge case with the new logs feature. In such cases, Sentry support recommends reaching out directly to their support team or via their Discord for further investigation Fields are being data-scrubbed ([Filtered]) which I am unable to debug and redact myself.

Summary of steps to take:

1. Double-check that both organization and project-level scrubbing (including default and advanced rules) are disabled.
2. Wait 20–30 minutes for settings to propagate.
3. Check the event JSON _meta section for the scrubbing reason.
4. If the issue persists, contact Sentry support with example events for further assistance.

Unfortunately, the knowledge sources do not provide a guaranteed workaround for this issue with the new logs feature if all scrubbing is truly disabled and [Filtered] still appears. This may require direct support from Sentry’s team.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

@lilac swallow Our robots are still learning and improving, please let us know if this response was correct by reacting below.

[lilac swallow]

There is no meta field that I can see in the logs

[toxic moat]

@lilac swallow mind DMing your org slug to me so the team can take a look