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

Configuring & Troubleshooting OTel YAML

On Linux, the Splunk OTel Collector reads /etc/otel/collector/agent_config.yaml and environment settings from splunk-otel-collector.conf.

Common ingestion failures trace back to four areas: invalid YAML indentation or forgotten component registration in service.pipelines, incorrect SPLUNK_ACCESS_TOKEN or SPLUNK_REALM (e.g., us0 vs us1 vs eu0), firewall blocks on outbound HTTPS port 443 or local OTLP ports (4317 for gRPC, 4318 for HTTP), and missing resourcedetection processors causing hosts to lack cloud or hostname dimensions.

To troubleshoot on Linux, inspect service status and logs with journalctl -u splunk-otel-collector, verify the health_check endpoint on localhost:13133, and inspect Collector internal telemetry or zPages to confirm datapoints are entering receivers and leaving exporters without 401/403 authentication errors.

Linux OTel Collector Troubleshooting Commands
sudo systemctl status splunk-otel-collector
sudo journalctl -u splunk-otel-collector -n 100 --no-pager
curl -s http://localhost:13133/
# Default OTLP ports: 4317 (gRPC), 4318 (HTTP)
If an OTel Collector starts cleanly with zero errors yet metrics never appear in Splunk IM, check whether the receiver and exporter were actually added to service.pipelines.metrics!

Knowledge Check

Prove your understanding to clear the room (Rewards XP)
❤️❤️❤️
Question 1 of 2
You add a new prometheus receiver under the receivers: section of agent_config.yaml and restart splunk-otel-collector, but zero Prometheus metrics reach Splunk Observability Cloud and no errors appear in journalctl. What is the most likely cause?
AThe prometheus receiver was not added to service.pipelines.metrics.receivers
BThe signalfx exporter only supports traces and cannot send Prometheus metrics
CPrometheus metrics require OTLP port 4317 to be opened inbound from the internet
DThe health_check extension blocks custom receivers by default