Extract client IP address and store it into context for OTLP/HTTP #4257
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.
Description:
Fixes otlphttp receiver so it adds information about the source IP into the context
Context: For k8sattributesprocessor the source IP is frequently required to associate the source with a given pod. This bug is emphasised now since SDK's are now encouraged to switch from gRPC to HTTP
Link to tracking Issue: #4256
Testing: Tested manually. I considered extending unit tests to cover this case, though I believe it would required including Context (as an array or the last one) in
consumertest.TracesSink
and I wasn't sure if it's a right thing to do.Documentation: Not changed