Splunk® Add-on for OpenTelemetry Collector

Splunk Add-on for OpenTelemetry Collector

Acrobat logo Download manual as PDF

Acrobat logo Download topic as PDF

Manage multiple collectors

If your configuration uses more than one collector, consider the following best practices:

  • Deploy different agent_config.yaml files to different hosts. For example, a version of the add-on with MySQL Receiver enabled, and a different version of the add-on with MS SQL Server Receiver enabled will work best when deployed on different hosts.
  • Deploy the same files to every host, then point to another agent_config.yaml file in inputs.conf in the splunk_config_dir or splunk_config_yaml properties.
  • Deploy the same instance of the Splunk Add-on for OpenTelemetry Collector to all hosts, then deploy another instance of the add-on that does not contain binaries and only contains a YAML file with a specific receiver enabled. In this case, the YAML file from the second add-on instance will supersede the YAML from the first add-on instance on a particular host.
  • Designate one instance of the Splunk Add-on for OpenTelemetry Collector as your default collector, tailor it to your needs, and then create variants of the add-on using a different name. Then deploy each variant to a different server class.
Last modified on 07 November, 2023
Configure the Splunk Add-on for OpenTelemetry Collector

This documentation applies to the following versions of Splunk® Add-on for OpenTelemetry Collector: 1.0, 1.0.1, 1.1.0, 1.2.0

Was this documentation topic helpful?

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters