The Splunk OTel Collector runs in two complementary topologies: local Agent mode (DaemonSet or host) and centralized Gateway mode.
In Agent mode (agent_config.yaml), one Collector runs on every Linux/Windows host or as a Kubernetes DaemonSet pod per node. Because it lives locally, the Agent scrapes hostmetrics, kubeletstats, and local application OTLP traffic over loopback, attaching node-specific metadata via resourcedetection.
In Gateway mode (gateway_config.yaml), Collectors run as a scalable Kubernetes Deployment behind a load balancer. Gateways do not scrape local host metrics; instead, they receive aggregated OTLP streams from multiple Agents, apply stateful or heavy transformations (such as attribute scrubbing, filtering, or trace tail_sampling), and centralize Splunk access tokens and outbound firewall egress.
[Host Apps + Node] -> OTel Agent (DaemonSet / systemd)
| (otlp gRPC :4317)
v
OTel Gateway (Deployment behind LB)
| (signalfx exporter + access token)
v
Splunk Observability Cloud Ingest