Handle sensitive query params in HTTP server instrumentation#16097
Handle sensitive query params in HTTP server instrumentation#16097trask merged 8 commits intoopen-telemetry:mainfrom
Conversation
3ee8792 to
64d9758
Compare
a96c83c to
4160a5a
Compare
| "paramA=valA¶mB=valB, paramA=valA¶mB=valB", | ||
| "AWSAccessKeyId=AKIAIOSFODNN7, AWSAccessKeyId=REDACTED", | ||
| "Signature=39Up9jzHkxhuIhFE9594DJxe7w6cIRCg0V6ICGS0%3A377, Signature=REDACTED", | ||
| "sig=39Up9jzHkxhuIhFE9594DJxe7w6cIRCg0V6ICGS0, sig=REDACTED", | ||
| "X-Goog-Signature=39Up9jzHkxhuIhFE9594DJxe7w6cIRCg0V6ICGS0, X-Goog-Signature=REDACTED", | ||
| "paramA=valA&AWSAccessKeyId=AKIAIOSFODNN7¶mB=valB, paramA=valA&AWSAccessKeyId=REDACTED¶mB=valB", | ||
| "AWSAccessKeyId=AKIAIOSFODNN7¶mA=valA, AWSAccessKeyId=REDACTED¶mA=valA", | ||
| "paramA=valA&AWSAccessKeyId=AKIAIOSFODNN7, paramA=valA&AWSAccessKeyId=REDACTED", | ||
| "AWSAccessKeyId=AKIAIOSFODNN7&AWSAccessKeyId=ZGIAIOSFODNN7, AWSAccessKeyId=REDACTED&AWSAccessKeyId=REDACTED", | ||
| "AWSAccessKeyId=AKIAIOSFODNN7#ref, AWSAccessKeyId=REDACTED#ref", | ||
| "AWSAccessKeyId=AKIAIOSFODNN7&aa&bb, AWSAccessKeyId=REDACTED&aa&bb", | ||
| "aa&bb&AWSAccessKeyId=AKIAIOSFODNN7, aa&bb&AWSAccessKeyId=REDACTED", | ||
| "AWSAccessKeyId=AKIAIOSFODNN7&&, AWSAccessKeyId=REDACTED&&", | ||
| "&&AWSAccessKeyId=AKIAIOSFODNN7, &&AWSAccessKeyId=REDACTED", | ||
| "AWSAccessKeyId=AKIAIOSFODNN7&a&b#fragment, AWSAccessKeyId=REDACTED&a&b#fragment" |
There was a problem hiding this comment.
essentially same test cases from HttpClientAttributesExtractorTest
| * | ||
| * @since 2.0.0 | ||
| */ | ||
| public final class UrlAttributesExtractor<REQUEST, RESPONSE> |
There was a problem hiding this comment.
(note: this class has no usages)
| List<String> newConfigValue = | ||
| httpConfig.getScalarList("sensitive_query_parameters", String.class); |
There was a problem hiding this comment.
let's block this PR on open-telemetry/semantic-conventions#3403
There was a problem hiding this comment.
Maybe it would be better to merge this PR using a temporary name. Could add experimental suffix/prefix or maybe even something like dontuse to indicate that it is subjected to change. This could let us avoid potential conflict resolution.
There was a problem hiding this comment.
Update: I'm trying to get this supported under the .general node by the next SDK release
There was a problem hiding this comment.
Update: this will be available in the upcoming SDK release
eb8f89e to
2795701
Compare
573747b to
ddd0d0f
Compare
ddd0d0f to
2204bae
Compare
No description provided.