The engine resolves transport_headers.header_propagation and installs the compiled policy on exporter effect handlers. OTLP/gRPC and Kafka exporters apply this policy, but the OTLP/HTTP exporter currently ignores it. As a result, headers captured into pdata context are silently lost when egress uses OTLP/HTTP.
Update the OTLP/HTTP exporter to use the schema-compiled context sink/propagation path when constructing requests, while preserving the zero-overhead path when no policy or context is present.
Acceptance criteria:
- Apply pipeline- and node-level
header_propagation selection, naming, and overrides.
- Define deterministic precedence for static exporter headers versus propagated headers.
- Handle invalid text or binary values explicitly rather than silently misencoding them.
- Reuse the compiled context propagation binding instead of adding another name-scanning implementation.
- Cover propagation, filtering, collisions, and the no-policy path.
The engine resolves
transport_headers.header_propagationand installs the compiled policy on exporter effect handlers. OTLP/gRPC and Kafka exporters apply this policy, but the OTLP/HTTP exporter currently ignores it. As a result, headers captured into pdata context are silently lost when egress uses OTLP/HTTP.Update the OTLP/HTTP exporter to use the schema-compiled context sink/propagation path when constructing requests, while preserving the zero-overhead path when no policy or context is present.
Acceptance criteria:
header_propagationselection, naming, and overrides.