You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having support for OTEL_EXPORTER_OTLP_HEADERS could unlock several scenarios. For example, we could support OTLP exporters that require header based authentication.
Spin should allow users to specify individual headers that will be used when emitting traces, logs, or metrics.
If the OTEL_EXPORTER_OTLP_HEADERS environment variable is present, Spin should configure outgoing headers on both TonicExporterBuilder and HttpExporterBuilder using the with_headers function
Having support for
OTEL_EXPORTER_OTLP_HEADERS
could unlock several scenarios. For example, we could support OTLP exporters that require header based authentication.Spin should allow users to specify individual headers that will be used when emitting traces, logs, or metrics.
If the
OTEL_EXPORTER_OTLP_HEADERS
environment variable is present, Spin should configure outgoing headers on bothTonicExporterBuilder
andHttpExporterBuilder
using thewith_headers
function(see https://docs.rs/opentelemetry-otlp/0.26.0/opentelemetry_otlp/struct.HttpExporterBuilder.html#method.with_headers for example)
More about
OTEL_EXPORTER_OTLP_HEADERS
:https://opentelemetry.io/docs/languages/sdk-configuration/otlp-exporter/#otel_exporter_otlp_headers
The text was updated successfully, but these errors were encountered: