Open bvsvas opened 3 months ago
Thanks @crobert-1 for your response. Yes, I tried it when I used the headers_setter
extension, but it didn't work with the loadbalancing
exporter. Probably it didn't work as the loadbalancing exporter aggregates multiple incoming requests into a group and sends different outbound requests??
I have updated the LB Collector configuration with the include_metadata
and headers_setter
extension in the Additional Context section. Could you review it and suggest if anything needs to be updated?
include_metadata
looks good to me. Is it working for you?
No.
Pinging code owners for exporter/loadbalancing: @jpkrohling. See Adding Labels via Comments if you do not have permissions to add labels yourself.
I need to try this out, I'm not sure this works at the moment.
Thanks @jpkrohling for looking into it. Your insights here are greatly appreciated.
@jpkrohling - I wanted to follow up and see if you had a chance to review the issue. We would greatly appreciate it if you could prioritize it when possible.
No, sorry, I have other things in my queue. Given that this seems important to you, it would help if you could go ahead and send a PR with a test case for this.
Component(s)
exporter/loadbalancing
What happened?
Description
Experiencing an issue with the loadbalancing exporter in OpenTelemetry Collector where incoming request headers (HTTP/gRPC) are not being forwarded to the downstream(second) collector. This behavior is critical for our use case, where headers such as Authorization need to be preserved throughout the request flow.
Steps to Reproduce
Expected Result
The loadbalancing exporter should forward all incoming request headers to the downstream collector by default.
Actual Result
The request headers are not being forwarded to the downstream collector.
Collector version
0.103.0
Environment information
Environment
OS: CentOS Kubernetes: 1.28 Deployment: Kubernetes Cluster Image: otel/opentelemetry-collector-contrib:0.103.0
OpenTelemetry Collector configuration
Log output
No response
Additional context
We have attempted using the headerssetter extension, but the issue persists. Any guidance on how to ensure headers are forwarded would be appreciated.