ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
The goal is to define a consistent expectation for graceful cancellation and timeout handling when using OpenTelemetry SDKs with OTLP exporters and a BatchSpanProcessor. Context cancellation in the application is propagated to in-flight operations but ending a span does not cancel its queued export. Export attempts are bounded by the exporter timeout setting
The OpenTelemetry OTLP exporter resolves the collector endpoint via the system DNS resolver before establishing a TLS connection. When the hostname cannot be resolved, the exporter logs an error and ceases sending telemetry until the application is restarted. Likewise, a failed TLS handshake due to an invalid or self‑signed certificate results in an immediat
Observed behavior When an application using the OpenTelemetry SDK with the OTLP exporter handles many concurrent requests, per-span export latency rises sharply compared to sequential traffic. The BatchSpanProcessor is documented to buffer spans and flush them when either maxExportBatchSize is reached or scheduleDelayMillis elapses, but under concurrency it
opentelemetry