Getting Started • Getting Involved • Migrating from Smart Agent
Architecture • Components • Monitoring • Security • Sizing • Troubleshooting
The Splunk Distribution of OpenTelemetry Collector provides a binary that can receive, process and export trace, metric and log data.
Installations that use this distribution can receive direct help from Splunk's support teams. Customers are free to use the core OpenTelemetry OSS components (several do!) and we will provide best effort guidance to them for any issues that crop up, however only the Splunk distributions are in scope for official Splunk support and support-related SLAs.
The Collector currently supports:
- Splunk APM via the
sapm
exporter. More information available here. - Splunk Infrastructure
Monitoring
via the
signalfx
exporter. More information available here. - Splunk Log Observer via
the
splunk_hec
exporter. - Splunk Cloud or
Splunk
Enterprise via
the
splunk_hec
exporter.
🚧 This project is currently in BETA.
The Collector provides a single binary and two deployment methods:
- Agent: A Collector instance running with the application or on the same host as the application (e.g. binary, sidecar, or daemonset).
- Gateway: One or more Collector instances running as a standalone service (e.g. container or deployment) typically per cluster, datacenter or region.
Use of the Collector running as an agent is only supported for the Splunk Observability Suite at this time. The SignalFx Smart Agent or Splunk Universal Forwarder should be used for all other products.
The Collector is supported on and packaged for a variety of platforms including:
- Kubernetes
- Linux
- Windows
You can consult additional use cases in the examples directory.