Server-side data scrubbing replaces Java object identifiers with [email] #4082
Description
Environment
self-hosted (https://develop.sentry.dev/self-hosted/)
Steps to Reproduce
Send a report with the following message, which is output by java.lang.management.ThreadInfo#toString and includes identifiers of Java objects that are currently locked. This is critical information in our deadlock reports.
"DeadlockSimulator1" prio=5 Id=30 BLOCKED on java.lang.Object@4b1c1ea0 owned by "DeadlockSimulator2" Id=31
at app//DeadlockNotifier.lambda$simulateDeadlock$0(DeadlockNotifier.java:130)
- blocked on java.lang.Object@4b1c1ea0
- locked java.lang.Object@74650e52
at app//DeadlockNotifier$$Lambda/0x00000e0001047a10.run(Unknown Source)
at java.base@25/java.lang.Thread.runWith(Thread.java:1487)
at java.base@25/java.lang.Thread.run(Thread.java:1474)
Expected Result
Leave the message as-is because it contains no sensitive data.
Actual Result
Sentry replaces the Java object identifiers (and also module identifiers in the stack trace) with [email], and now I can't tell what the locked objects are.
"DeadlockSimulator1" prio=5 Id=30 BLOCKED on [email] owned by "DeadlockSimulator2" Id=31
at app//DeadlockNotifier.lambda$simulateDeadlock$0(DeadlockNotifier.java:130)
- blocked on [email]
- locked [email]
at app//DeadlockNotifier$$Lambda/0x00000e0001047a10.run(Unknown Source)
at [email]/java.lang.Thread.runWith(Thread.java:1487)
at [email]/java.lang.Thread.run(Thread.java:1474)
There appears to be no way to configure the default scrubbing, to for example disable only email scrubbing, so the only option appears to be to disable scrubbing entirely.
Product Area
Unknown
Link
No response
DSN
No response
Version
25.8.0