Use Splunk Distribution of OpenTelemetry Collector 🔗
This page provides a list of resources for using the Splunk OpenTelemetry Collector.
This project is currently in Beta. See Beta Definition for more information.
Refer to the following topics for an overview of the Collector:
Architecture, which describes how to deploy the Collector.
Components, which describes what the Collector supports.
Monitoring, which describes how to ensure that the Collector is healthy.
Security, which describes how to ensure that the Collector is secure.
Sizing, which describes how to ensure that the collecor is properly sized.
Troubleshoot the Collector, which describes how to resolve common issues with the Collector.
Getting started 🔗
You need the following resources to get started using the Collector:
Confirm exposed ports to make sure your environment doesn’t have conflicts and that firewalls are configured properly. Ports can be changed in the configuration.
This distribution is supported on and packaged for a variety of platforms, including:
See examples for additional use cases.
The following is a list of default configuration files. These files contain standard specifications and settings.
signalfx/splunk-otel-collector. full_config_linux.yaml includes comments and links to documentation. agent_config_linux.yaml is the recommended starting configuration for most environments.
Fluentd, which is only applicable to Helm or installer script installations. See the
*.conffiles and the
conf.ddirectory. Common sources, including filelog, journald, and Windows Event Viewer are included.
Custom configuration 🔗
Upstream OpenTelemetry Collector 🔗
It is possible to use the upstream OpenTelemetry Collector instead of this Splunk Distribution of OpenTelemetry Collector. The following features are not available upstream at this time:
Packaging, including installer scripts for Linux and Windows, and configuration management using Ansible or Puppet
Several Smart Agent capabilities
Splunk only provides best-effort support for the upstream OpenTelemetry Collector.
Do the following to use the upstream OpenTelemetry Collector:
Use the OpenTelemetry Collector contribution. This contribution includes receivers/exporters and components that are vendor specific.
Configure the upstream OpenTelemetry Collector.