⛏️GetSplunky!
Lv.1Intern
0 XP
0
Home Map Stats Drill Board Log In
CoursesArticlesSPL Cheat SheetCertification PathAboutPrivacyTerms

Splunky is an independent, free study resource. It is not affiliated with, endorsed by, or sponsored by Splunk or Cisco. Splunk, SPL and related marks are trademarks of Splunk, a Cisco company, and are used here only to identify the certifications this site helps you study for.

© 2026 Splunky

Back to Floor
The Telemetry Pipeline • Room 1

Receivers, Processors, Exporters & Extensions

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.

OTel Collector Pipeline Flow
service:
  extensions: [health_check, zpages]
  pipelines:
    metrics:
      receivers: [hostmetrics, otlp]
      processors: [memory_limiter, resourcedetection, batch]
      exporters: [signalfx]
Always list memory_limiter as the FIRST processor in every pipeline so the Collector drops or throttles excess telemetry cleanly instead of crashing with an Out-Of-Memory (OOM) error.

Knowledge Check

Prove your understanding to clear the room (Rewards XP)
Drag items to their correct zone (or tap item then tap zone on mobile)
hostmetrics / otlp / prometheus components that pull or listen for incoming telemetry
memory_limiter / batch / resourcedetection components that protect memory, enrich, and compress
signalfx / otlphttp components that transmit metrics and traces to Splunk Observability Cloud
health_check / zpages components providing Collector readiness endpoints and diagnostics
1. Receiver (Ingest)
2. Processor (Transform)
3. Exporter (Egress)
4. Extension (Support)