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
I think it would be a great addition to add a configuration option to enable the obfuscation of path parameters.
While I found the possibility to obfuscate query params (DD_TRACE_OBFUSCATION_QUERY_STRING_REGEXP), I did not find the such a possibility for path parameters. It would be great to be able to specify a regex and a replacement text for a resource.
Is your feature request related to a problem?
Unfortunately, an API I depend on expects Personally identifiable information as a path parameter. Without the possibility to obfuscate the path parameter, I cannot benefit from the APM for this call because I would have to ignore it.
Describe alternatives you've considered
No response
Additional context
I have seen that DD_APM_OBFUSCATION_HTTP_REMOVE_PATHS_WITH_DIGITS exists. Unfortunately, this option is insufficient for my case, as the path parameter is alphanumeric and not just numeric.
The text was updated successfully, but these errors were encountered:
Library Name
No response
Library Version(s)
No response
Describe the feature you'd like
I think it would be a great addition to add a configuration option to enable the obfuscation of path parameters.
While I found the possibility to obfuscate query params (DD_TRACE_OBFUSCATION_QUERY_STRING_REGEXP), I did not find the such a possibility for path parameters. It would be great to be able to specify a regex and a replacement text for a resource.
Is your feature request related to a problem?
Unfortunately, an API I depend on expects Personally identifiable information as a path parameter. Without the possibility to obfuscate the path parameter, I cannot benefit from the APM for this call because I would have to ignore it.
Describe alternatives you've considered
No response
Additional context
I have seen that
DD_APM_OBFUSCATION_HTTP_REMOVE_PATHS_WITH_DIGITS
exists. Unfortunately, this option is insufficient for my case, as the path parameter is alphanumeric and not just numeric.The text was updated successfully, but these errors were encountered: