Observability

OpenTelemetry Collector Pipeline Guide

Build and troubleshoot OpenTelemetry Collector receiver, processor and exporter pipelines without hiding dropped telemetry. Last updated September 17, 2026.

Build and troubleshoot OpenTelemetry Collector receiver, processor and exporter pipelines without hiding dropped telemetry. This reference is written for developers who need practical validation behavior, reviewable rules and safe examples rather than copied snippets with no explanation.

Recommended workflow

Step	Why it matters
Start with one signal	Prove a small traces or metrics pipeline before combining every receiver.
Order processors	Memory limits, filtering, enrichment and batching have different failure effects.
Expose collector metrics	Queue size, refused items and exporter failures reveal pressure early.
Test failure behavior	Disconnect the backend and confirm retry, queue and data-loss expectations.

Starter snippet

receivers -> memory_limiter -> batch -> redaction -> exporters

Review checks

Set memory limits below the container limit.
Use bounded sending queues.
Keep credentials in environment-backed secrets.
Validate configuration before deployment.

Common mistakes

Adding retries without queue limits.
Filtering telemetry before measuring what was removed.
Running one collector pipeline with no health endpoint.

Validation should help users correct input while protecting systems from bad data. Keep syntax checks, product policy, security review and deliverability checks separate.

Related Formalint references

Continue with OpenTelemetry Trace Debugging, Docker Container Logs Guide, Kubernetes Pod Debugging Guide.