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.
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)