⛏️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 3

Host, Kubernetes & Prometheus Scraping

The Splunk OTel Collector ingests infrastructure metrics via dedicated receivers for Linux hosts, Kubernetes clusters, and Prometheus targets.

The hostmetrics receiver collects OS-level CPU, memory, disk, filesystem, load, and network metrics directly from Linux /proc and sysfs. In Kubernetes, kubeletstats pulls pod and container resource metrics from the local node Kubelet API, while k8s_cluster gathers cluster-wide state (deployments, replica sets, node conditions) from the Kubernetes API server.

For applications already instrumented with Prometheus client libraries, the prometheus receiver scrapes /metrics endpoints on configured scrape_configs intervals, translating Prometheus gauges and counters into OTLP metrics without rewriting application code. All collected metrics are commonly exported to Splunk Infrastructure Monitoring via the signalfx exporter.

Linux & Prometheus OTel Collector Receivers
receivers:
  hostmetrics:
    collection_interval: 10s
    scrapers:
      cpu:
      memory:
      disk:
  prometheus:
    config:
      scrape_configs:
        - job_name: "app-metrics"
          scrape_interval: 10s
          static_configs:
            - targets: ["localhost:9090"]
Match collection_interval and scrape_interval to 10s (Splunk IM default native resolution) unless you explicitly pay for 1s high-resolution ingestion.

Knowledge Check

Prove your understanding to clear the room (Rewards XP)
Complete this Splunk OTel Collector YAML snippet to scrape local host metrics and Prometheus endpoints, then export them to Splunk Infrastructure Monitoring:
receivers:
:
collection_interval: 10s

:
config:

scrape_configs:

- job_name: "orders-service"

exporters:

:
access_token: "${SPLUNK_ACCESS_TOKEN}"

realm: "us1"