How can I make a OpenTelemetry setup reproducible?
The same project needs to behave consistently on developer machines, in CI and after deployment. Which versions, dependencies and configuration should be recorded?
Loading…
ReadMeFeed / Community knowledge
OpenTelemetry
Real questions. Useful conversations. Find the people who know your stack.
OpenTelemetry
Developer tools · #opentelemetry
How should I approach a OpenTelemetry upgrade?
An upgrade needs a compatibility check, a tested release and a recovery path. Which changes deserve particular attention before the new version reaches production?
OTLP Exporter Resource Attribute Persistence During Batch Processing
Resource Attribute Handling in OTLP Pipelines The OpenTelemetry Collector utilizes a pipeline architecture where telemetry signals are passed from receivers through processors to exporters. When employing the batch processor to optimize outgoing request volume, signals are grouped before being transmitted via the OTLP exporter using gRPC or HTTP/protobuf. A
OTLP Exporter Stops Sending Data When DNS Resolution Fails
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
Span ends prematurely on context cancellation in OpenTelemetry SDK
When a request context is cancelled while an OpenTelemetry span is still active, the SDK is expected to end the span, but the exact moment of span completion relative to the cancellation signal varies between language implementations. The OpenTelemetry Specification defines cancellation propagation but does not prescribe how instrumentation should record par
How should I handle configuration and secrets in OpenTelemetry?
Configuration must be available to the application without exposing credentials in source control, logs or browser code. What belongs in the runtime and which access controls matter?
What should I check first when OpenTelemetry fails?
A failure needs to be narrowed down before settings are changed or operations retried. Which evidence best separates application errors from environment and dependency problems?
Should OpenTelemetry expose a dedicated API for configuring per-span timeouts instead of relying only on context propagation?
Determine whether OpenTelemetry should provide a dedicated API for configuring timeouts on individual spans, rather than relying exclusively on context‑propagated deadlines. The specification leaves the exact moment a span is considered “ended” versus “aborted” to each SDK implementation, leading to differences in recorded duration and attributes after a can
Runtime Adjustment of OpenTelemetry Probability Sampler: Unclear Mechanism
Problem OpenTelemetry auto‑instrumentation libraries default to a probability sampler (often 10% for Java, 5% for Python) to limit trace volume. The SDK exposes a sampler configuration API, but changing the sampler at runtime requires code changes or a restart; no cross‑language, environment‑variable override is defined in the core spec. Vendor exporters (Ja