You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given the sensitive nature of this information, SDKs and exporters SHOULD drop these attributes by default and then provide a configuration parameter to turn on retention for use cases where the information is required and would not violate any policies or regulations.
However, the existing servlet instrumentation currently captures the enduser.id attribute in a couple places (here and here) by default, without requiring the user to explicitly enable those attributes.
Steps to reproduce
Execute an authenticated request against a servlet based application.
Observe enduser.id attribute captured by default.
Expected behavior
I expect the enduser.id attribute to not be captured by default.
I expect that I am required to explicitly enable capturing of the enduser.id attribute.
Actual behavior
enduser.id attribute captured by default without requiring the user to explicitly enable it.
Javaagent or library instrumentation version
1.31.0
Environment
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
philsttr
changed the title
enduser.id should not be captured by default for servlet applications
enduser.id should not be captured by default
Oct 23, 2023
Describe the bug
The General Identity Attributes convention for
enduser.*
attributes states:However, the existing servlet instrumentation currently captures the
enduser.id
attribute in a couple places (here and here) by default, without requiring the user to explicitly enable those attributes.Steps to reproduce
enduser.id
attribute captured by default.Expected behavior
I expect the
enduser.id
attribute to not be captured by default.I expect that I am required to explicitly enable capturing of the
enduser.id
attribute.Actual behavior
enduser.id
attribute captured by default without requiring the user to explicitly enable it.Javaagent or library instrumentation version
1.31.0
Environment
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: