Diagnosing OpenTelemetry Collector OTLP Exporter Failures
A step‑by‑step diagnostic guide for when spans or metrics never reach your backend — covering network, TLS, auth, batching, and protocol mismatches.
Loading…
ReadMeFeed / Community knowledge
#collector
Real questions. Useful conversations. Find the people who know your stack.
opentelemetryArchitecture Note: Tail Sampling with the OpenTelemetry Collector
A two-tier OpenTelemetry Collector design: local agents export OTLP to a gateway that runs tail_sampling, preserving errors and slow traces while bounding cost and blast radius.
Designing an OpenTelemetry Collector OTLP/HTTP Exporter with Mutual TLS and Retry Logic
Shows the minimal Collector exporter setup that secures telemetry with mTLS, batches spans, and retries failures, plus how to monitor and adapt the design.
Scaling OpenTelemetry Pipelines: Batch Processor Meets Memory Limiter
Pairing OpenTelemetry Collector's batch processor with the memory limiter lets you scale telemetry throughput without OOM kills or dropped spans. The key: memory limiter first, batch second, and sizing both against your backend's actual limits.
Building a Custom Java Stream Collector for Department‑wise Average Salary
Learn how to create a Java Stream Collector that groups employees by department and computes average salary, with notes on thread‑safety and verification.
javaOpenTelemetry Collector Tail Sampling: Reduce Ingestion Costs While Keeping Errors and Slow Traces
Use the OpenTelemetry Collector's Tail Sampling Processor to keep errors and slow traces while probabilistically sampling the rest. This guide covers a working configuration, policy ordering, memory limits, and common placement mistakes.
Configure OpenTelemetry Collector to Ingest OTLP and Export to Jaeger, Prometheus, and Loki
Learn how to set up the OpenTelemetry Collector to receive OTLP traces and metrics and forward them to Jaeger, Prometheus, and Loki with proper batching, retry logic, and resource attribution. Follow a step‑by‑step guide, validate the pipeline, and recover from common issues.
prometheusOTLP Receiver to OTLP Exporter: Does the OpenTelemetry Collector preserve incoming W3C tracestate entries unchanged?
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
Behavior of OpenTelemetry Collector batch processor flush during shutdown with limited timeout
Goal: ensure that when the OpenTelemetry Collector receives a shutdown signal, all spans and metrics held in the batch processor are exported without loss. Constraints: the batch processor flushes its queue on shutdown but only for a configurable timeout; if the timeout expires before the queue is drained, remaining items may be dropped. Meanwhile, the proce