Passing header from jaeger exporter

[ankitnayan]

I am currently sending data using

OTEL_SERVICE_NAME='<service name>' OTEL_EXPORTER_JAEGER_ENDPOINT="http://<IP of  Backend>:14268/api/traces" opentelemetry-instrument -e jaeger python program.py

Is there a way to pass headers in the above command?

I am using HTTP to send data to otel-collector and want to pass a header with every request. OTLP has the option to pass headers but right now the OTLP exporter allows only GRPC communication.
The Jaeger exporter supports HTTP but couldn't find a way to pass headers.

Is there a way to achieve this using Jaeger, OTLP, or any other exporters?

[srikanthccv]

There is no way to do that with Jaeger or Zipkin exporters as of now. You are right about OTLP exporter supporting gRPC only. OTLP exporters uses metadata for sending OTEL_EXPORTER_OTLP_HEADERS so if you really need the custom headers you may want to use gRPC for sending data until other formats support added. There is a plan to add JSON/HTTP and Protobuf/HTTP. Probably we will have them implemented for RC2 because an exporter needs to support at least one for RC1. There was a discussion around this in the SIG meeting. I will bring this up this again to get more clarity.

[ankitnayan]

thanks for the clarification..the only possible way to do this right now seems to be via Otel-Collector, which can transmit in OTLP HTTP with headers right?

[srikanthccv]

thanks for the clarification..the only possible way to do this right now seems to be via Otel-Collector, which can transmit in OTLP HTTP with headers right?

Yes

[srikanthccv]

@ankitnayan You may want to close this issue for now and subscribe to releases of this repo unless you have something else to add.

[codeboten]

@ankitnayan is the request here to be able to pass custom headers to be exported to jaeger? if so I think the right place to suggest this would be in the specification repo so that all implementations are consistent.