Enable configured OpenTelemetry components in the service section

A receiver definition can exist in the file without participating in any running pipeline.

Source facts

OpenTelemetry Collector configuration separates component definitions from activation. Defining a receiver does not enable it; it must be referenced in an appropriate service pipeline. Processors also need to be added to appropriate service pipelines. Exporters likewise need to be added to appropriate service pipelines. Extensions are enabled through the service section rather than ordinary telemetry pipelines.

Source: OpenTelemetry documentation — Configuration.

Applicability

Review configured Collector component activation through the service pipelines and extension configuration.

DSE recommendation

DSE recommends drawing the intended receive-process-export path and comparing every component reference with the actual configuration. Keep instance identifiers consistent when several components share a type. Review the service section during troubleshooting instead of repeatedly changing an unused component block. Confirm the installed distribution and version before selecting examples. Treat configuration validation, successful startup, and observed data flow as separate acceptance steps so a process that starts without using the intended pipeline is not declared complete.

Verification

In a test Collector, inspect the configured pipeline and send a harmless known signal through it. Compare behavior with a deliberately unreferenced receiver definition. Confirm each intended component is active and the signal reaches the approved destination, then remove temporary diagnostic outputs and unused definitions. Retain the effective service references with the known sample’s route. Ask the pipeline owner to trace that sample from the intended receiver through each enabled processor to its exporter before accepting a configuration-only success.

Official reference

OpenTelemetry documentation — Configuration. Reviewed October 20, 2026.