Docs » Install and configure Splunk Distribution of OpenTelemetry Collector » Install the collector

Install the collector 🔗

Splunk Distribution of OpenTelemetry Collector is supported on and packaged as a connector for Kubernetes, Linux, and Windows. The connector is a package that provides integrated collection and forwarding for all data types for a specific platform. Connector refers to packaging only, which is separate from the standalone Splunk Distribution of OpenTelemetry Collector. The connector includes the Splunk Distribution of OpenTelemetry Collector.

Deploy one of the following connectors to gather data for Infrastructure Monitoring, APM, and Log Observer:

  • Splunk OpenTelemetry Connector for Kubernetes or splunk-otel-collector-chart

  • Splunk OpenTelemetry Connector for Linux or splunk-otel-collector

  • Splunk OpenTelemetry Connector for Windows or splunk-otel-collector

The connector uses these components to access data.




Receivers, which can be push or pull based, is how data gets into the collector. Receivers support one or more data sources. You must configure one or more receivers. By default, no receivers are configured.


Processors sit between receivers and exporters, reading and sometimes operating on data as it flows through the pipeline. Processors are optional, but you should include processors in your configuration. The order in which processors are listed in the processors section of the configuration is significant.


An exporter, which can be push or pull based, is how you send data to one or more destinations. Exporters support one or more data sources.

Once configured, enable these components using pipelines within the service section of the configuration. The service section contains two subsections: extensions and pipelines. The extensions section is where you optionally enable any extensions you have configured, and the pipelines section is where you define one or more pipelines, each of which consists of receivers, processors (optional), and exporters. The service section’s two subsections are described in the following table.




Provide capabilities that can be added to the collector, but which do not require direct access to telemetry data and are not part of pipelines.


Pipelines can be traces, metrics, or logs. Pipelines consist of a set of receivers, processors, and exporters. Each receiver, processor, and exporter must be defined in the configuration outside of the service section to be included in a pipeline.

Next, install the connector for your platform. See Install on Kubernetes, Install on Linux, or Install on Windows.