ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
The goal is to confirm whether an OpenTelemetry Collector, when receiving spans through an OTLP receiver from an SDK‑instrumented service, forwards the original W3C traceparent and tracestate headers unchanged via its OTLP exporter to a downstream backend. This concerns the preservation of trace context across the Collector boundary. The OTLP specification d
The OpenTelemetry Collector operates as a stateless intermediary, exporting telemetry via OTLP to various storage backends like ClickHouse or Prometheus. While the collector handles data buffering and retry logic, it lacks native mechanisms to verify the integrity of data sets after a backend-side backup restoration has occurred. Because the collector typica
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
opentelemetry