The Splunk OpenTelemetry (OTel) Collector is the vendor-neutral agent for ingesting metrics, traces, and logs into Splunk Observability Cloud.
Every OTel Collector configuration YAML file defines component sections—receivers, processors, exporters, and extensions—and wires them together inside the service.pipelines block. Data flows strictly from receivers (ingestion) through an ordered list of processors (transformation, batching, memory protection) out to exporters (backend delivery).
Extensions run alongside pipelines to provide operational capabilities such as health checks (/healthz on port 13133), zPages diagnostics, and service discovery observers (host_observer, k8s_observer). Defining a component under receivers or processors alone does nothing until it is referenced inside service.pipelines.
service:
extensions: [health_check, zpages]
pipelines:
metrics:
receivers: [hostmetrics, otlp]
processors: [memory_limiter, resourcedetection, batch]
exporters: [signalfx]