Fixes configuration logic for netty-4.1.16 module #2355
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Fixes a bug in the internal netty config.
Expected behavior:
Setting this config to
false
(which is the default value) should resolve 'unknown' transactions in netty at the cost of less granularity when instrumenting HTTP2 web transactions.Setting the config to
true
causes the 'unknown' transactions to resurface but we get more granularity with HTTP2 transactions.Description of the bug:
Setting the below config to false causes the 'unknown' transactions to appear again but setting it to
true
resolves it but HTTP2 is no longer supported.Solution:
One of the boolean values in the netty instrumentation was flipped. By switching that value, we resolve this issue.