Deploy the Collector for Windows with Puppet
Install the Splunk Distribution of OpenTelemetry Collector on Windows using Puppet.
Follow these instructions to use Puppet to install and configure the Collector on Windows.
Download Puppet
-
Download and install Puppet from Splunk's JFrog Artifactory instance:
- Connect Puppet to Artifactory
-
Add the following snippet to your puppet.conf file:
BASH[main] module_repository=https://splunk.jfrog.io/artifactory/api/puppet/puppet-splunk - r10k
-
To configure r10k to fetch modules from Artifactory, add the following to your r10k.yaml file:
BASHforge: baseurl: https://splunk.jfrog.io/artifactory/api/puppet/puppet-splunk - Command line
-
BASH
puppet module install --module_repository=https://splunk.jfrog.io/artifactory/api/puppet/puppet-splunk signalfx-splunk_otel_collector
-
On Windows systems, be sure to download these required Puppet modules:
-
puppetlabs/registry module is required to set the registry key/values.
-
puppetlabs/powershell module is required to run PowerShell commands.
-
Configure Puppet
You customize Puppet using the class parameter.
To use this module, include the splunk_otel_collector class in your manifests with any supported parameters.
For example, the following deployment definition is the simplest deployment definition with the default parameters:
class { splunk_otel_collector:
collector_version => 'your-collector-version'
splunk_access_token => 'your-splunk-access-token',
splunk_realm => 'your-splunk-realm',
}
Replace your-collector-version with the desired Collector version, your-splunk-access-token with your Splunk access token to authenticate requests, and your-splunk-realm for the realm to send the data to.
Puppet parameter reference
The class object accepts the parameters described in the following table:
|
Name |
Description |
Default value |
|---|---|---|
|
|
Version of the Collector package to install, for example, |
None |
|
|
Replaces |
90% of |
|
|
The Splunk access token to authenticate requests. This attribute is required. |
None |
|
|
Which realm to send the data to, for example, |
None |
|
|
Sets the Splunk ingest URL explicitly instead of the URL inferred by the |
|
|
|
Sets the Splunk API URL explicitly instead of the URL inferred by the |
|
|
|
Sets the Splunk trace endpoint URL explicitly instead of the URL inferred by the |
|
|
|
Sets the Splunk HEC endpoint URL explicitly instead of the URL inferred by the |
|
|
|
Sets the Splunk HEC authentication token if different than |
|
|
|
The path to the Smart Agent bundle directory. The default path is provided by the Collector package. If the specified path is changed from the default value, the path should be an existing directory on the node. The |
|
|
|
The path to the collectd configuration directory for the Smart Agent bundle. The default path is provided by the Collector package. If the specified path is changed from the default value, the path should be an existing directory on the node. The |
|
|
|
Total memory in MIB to allocate to the Collector; automatically calculates the ballast size. The |
|
|
|
|
None |
|
|
The source path to the Collector configuration YAML file. This file is copied to the |
|
|
|
Destination path of the Collector configuration file on the node. The |
|
Next steps
After you have installed the package, see:
-
View logs and errors in the Windows Event Viewer. Search for "view logs and errors" on the Microsoft documentation site for more information.