Skip to content

Commit 345407e

Browse files
sfanahataShannon Anahata
andauthored
update advanced scrubbing doc - adding logs section (#14696)
## DESCRIBE YOUR PR * New section in advanced data scrubbing doc. Preview: https://sentry-docs-git-advanced-data-scrubbing-updates.sentry.dev/security-legal-pii/scrubbing/advanced-datascrubbing/#data-scrubbing-for-logs ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. - [x] Urgent deadline (GA date, etc.): 8.26.2025 - [ ] Other deadline: <!-- ENTER DATE HERE --> - [ ] None: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it. Thanks in advance for your help! ## PRE-MERGE CHECKLIST *Make sure you've checked the following before merging your changes:* - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) Co-authored-by: Shannon Anahata <[email protected]>
1 parent 7693a15 commit 345407e

File tree

4 files changed

+18
-0
lines changed

4 files changed

+18
-0
lines changed

docs/security-legal-pii/scrubbing/advanced-datascrubbing.mdx

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -233,3 +233,21 @@ The following limitations generally apply to all server-side data scrubbing, be
233233
- Sentry's internals require that the event user's IP address must either be `null` or a valid IPv4/IPv6 address. If you're trying to hash, mask or replace IP addresses, data scrubbing will move the replacement value into the user ID (if one is not already set) in order to avoid breaking this requirement while still providing useful data for the Users count on an issue.
234234

235235
- In stack traces, scrubbing works on file paths but not on a file's base name. This would violate assumptions in the processing pipeline resulting in a poor user experience. Instead, you can scrub a file's base name in the SDK itself, using the [`RewriteFrames` integration](https://docs.sentry.io/platforms/javascript/configuration/integrations/rewriteframes/) or [`beforeSend`](https://docs.sentry.io/platforms/javascript/configuration/filtering/).
236+
237+
## Data Scrubbing for Logs
238+
239+
[Logs](/product/explore/logs/) will honor the default [Server-Side Data Scrubbing rules](/security-legal-pii/scrubbing/server-side-scrubbing/#geographic-information) applied to your projects. To add advanced data scrubbing rules for Logs, start by choosing the dataset.
240+
241+
![Add an advanced data scrubbing rule dialog showing dataset selection, method, data type, and source fields](img/data_scrub_rule.png)
242+
243+
<Alert>
244+
Deep wild cards ('**') or $string / $number value selectors will apply across all datasets. For specific data types you can select the log attribute that needs to be scrubbed.
245+
</Alert>
246+
247+
![Attribute field with auto-completion dropdown showing available log attributes](img/scrub_attribute.png)
248+
249+
You can also edit existing scrubbing rules
250+
251+
![Edit dialog showing an existing rule with custom placeholder and attribute configuration](img/scrub_edit.png)
252+
253+
25.6 KB
Loading
29.1 KB
Loading
25.2 KB
Loading

0 commit comments

Comments
 (0)