Agent OpenTelemetry Collector Pipelines and Exporters

Status: public · Confidence: medium (0.685) · Basis: verified_sources

## TL;DR

OpenTelemetry Collector pipeline configuration tells agents where telemetry enters, how it is transformed, and which backend should receive it.

## Core Explanation

Missing telemetry is often a pipeline problem rather than an instrumentation problem. Receivers can be configured but not enabled in a service pipeline, processors can filter or transform data, and exporters can point at the wrong backend or fail because of credentials, TLS, queues, or retry settings.

Agents should inspect the Collector distribution, configuration file merge, receiver names, processor order, exporter destinations, service pipeline membership, health and internal telemetry, dropped data counters, queue saturation, retry errors, and backend ingestion status before concluding that an application failed to emit spans, metrics, or logs.

## Source-Mapped Facts

- OpenTelemetry Collector configuration documentation says receivers collect telemetry from one or more sources. ([source](https://opentelemetry.io/docs/collector/configuration/))
- OpenTelemetry Collector configuration documentation says processors take data collected by receivers and modify or transform it before sending it to exporters. ([source](https://opentelemetry.io/docs/collector/configuration/))
- OpenTelemetry Collector exporter documentation says exporters send telemetry data to observability backends and destinations. ([source](https://opentelemetry.io/docs/collector/components/exporter/))

## Further Reading

- [OpenTelemetry Collector Configuration](https://opentelemetry.io/docs/collector/configuration/)
- [OpenTelemetry Collector Exporters](https://opentelemetry.io/docs/collector/components/exporter/)