Skip to content

Commit 8fd3e58

Browse files
jjbayerDav1dde
andauthored
Clarify limitations of attachment scrubbing (#12281)
Co-authored-by: David Herberth <[email protected]>
1 parent 9aafe96 commit 8fd3e58

File tree

1 file changed

+15
-1
lines changed

1 file changed

+15
-1
lines changed

docs/security-legal-pii/scrubbing/attachment-scrubbing.mdx

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,21 @@ All attachments can be selected using the `$attachments` [Value Type](../advance
3232
The filename must be in quotes to write a specific filename, but wildcards can also be used.
3333

3434
For example, for the filename `minidump.dmp`, you can select all fields to be scrubbed using `$attachments.'minidump.dmp'.**`.
35-
To write the same using a wildcard to select all attachments, you would write `$attachments.*.**` or even simply `$attachments.**`.
35+
To write the same using a wildcard to select attachments with a specific file name, you would write `$attachments.'my_file.txt'.**` or even simply `$attachments.'my_file.txt'`.
36+
37+
<Alert level="warning" title="Attachment scrubbing limitations">
38+
39+
Sentry currently only has limited support for scrubbing attachments that are not minidumps. Only attachments that are explicitly selected by an [Advanced Data Scrubbing](../advanced-datascrubbing/) rule with a non-wildcard filename will actually be scrubbed. For example:
40+
41+
```
42+
# Will be scrubbed:
43+
[Remove] [IP Addresses] from [$attachments.'foo.txt']
44+
45+
# Will NOT be scrubbed:
46+
[Remove] [IP Addresses] from [$attachments.**]
47+
```
48+
49+
</Alert>
3650

3751
### Minidump Selectors
3852

0 commit comments

Comments
 (0)