Install the Collector for Windows with the installer script 🔗
The Splunk Distribution of the OpenTelemetry Collector for Windows is a package that provides integrated collection and forwarding for all data types. Read on to see how to install it using the installer script.
Note
The Splunk Distribution of the OpenTelemetry Collector comes with a default configuration, as detailed in Collector for Windows default configuration. To modify this configuration, refer to Advanced configuration for Windows.
To learn how to obtain logs, see Collect logs with the Collector for Windows.
Alternatively, you can also install the Collector for Windows:
Using MSI. See Install the Collector for Windows using the MSI installer.
Using deployment tools. See Install the Collector for Windows using deployment tools.
Manually. See Install the Collector for Windows manually.
Prerequisites 🔗
The Collector supports the following Windows versions, depending on the installation method:
Install method |
Supported versions (64-bit) |
|---|---|
Installer script |
Windows 10 Pro and Home, Windows Server 2016, 2019, 2022 |
Windows installer (MSI) |
Windows 10 Pro and Home, Windows Server 2016, 2019, 2022 |
Ansible |
Windows 10 Pro and Home, Windows Server 2016, 2019, 2022 |
Chef |
Windows 10 Pro and Home, Windows Server 2019, 2022 |
Nomad |
Windows 10 Pro and Home, Windows Server 2016, 2019 |
Puppet |
Windows 10 Pro and Home, Windows Server 2016, 2019 |
Docker |
Windows 10 Pro and Home, Windows Server 2019, 2022 |
Note
PowerShell 3.0 or higher is required.
Included packages 🔗
The Windows installer script installs the following packages:
Dotnet autoinstrumentation, if enabled. See Instrument .NET applications for Splunk Observability Cloud (OpenTelemetry).
Fluentd, if enabled. See Collect Windows logs with Fluentd.
JMX metric gatherer.
For Docker environments only, Java JDK and JRE.
Install the Collector for Windows using the installer script 🔗
The installer script is available for Windows 64-bit environments, and deploys and configures:
The Splunk Distribution of the OpenTelemetry Collector for Windows
Fluentd through the
td-agent, which is deactivated by default
To install the package using the installer script, follow these steps:
Ensure that you have Administrator access on your host.
Run the following PowerShell command on your host, replacing the following variables for your environment:
SPLUNK_REALM: This is the realm to send data to. The default isus0. See realms .SPLUNK_ACCESS_TOKEN: This is the base64-encoded access token for authenticating data ingest requests. Your access token needs to have the ingest authorization scope. See Create and manage organization access tokens using Splunk Observability Cloud.
& {Set-ExecutionPolicy Bypass -Scope Process -Force; $script = ((New-Object System.Net.WebClient).DownloadString('https://dl.signalfx.com/splunk-otel-collector.ps1')); $params = @{access_token = "SPLUNK_ACCESS_TOKEN"; realm = "SPLUNK_REALM"}; Invoke-Command -ScriptBlock ([scriptblock]::Create(". {$script} $(&{$args} @params)"))}
If you need to activate TLS in PowerShell, use the command:
[Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Tls12
Caution
Starting from version 0.89, the installer for the Splunk Distribution of the OpenTelemetry Collector for Windows sets its configuration using environment variables at service level instead of global level. To configure additional settings use service, process, or terminal scopes.
Start the Collector executable manually 🔗
If you experience unexpected start failures, try to start the Collector executable manually.
To do so, run the following PowerShell command as an Admin:
& 'C:\Program Files\Splunk\OpenTelemetry Collector\otelcol.exe' --config 'C:\ProgramData\Splunk\OpenTelemetry Collector\agent_config.yaml'
Options of the installer script for Windows 🔗
The Windows installer script supports the following options:
Option |
Description |
Default value |
|---|---|---|
|
The token used to send metric data to Splunk. |
|
|
The Splunk realm to use. The ingest, API, trace, and HEC endpoint URLs are automatically created using this value. To find your Splunk realm, see Note about realms. |
|
|
Total memory in MIB to allocate to the Collector. Automatically calculates the ballast size. See Sizing and scaling for more information. |
|
|
Configure the Collectorservice to run in host monitoring ( |
|
|
The network interface the Collectorreceivers listen on. |
|
|
Set the base ingest URL explicitly instead of the URL inferred from the specified realm. |
|
|
Set the base API URL explicitly instead of the URL inferred from the specified realm. |
|
|
Set the trace endpoint URL explicitly instead of the endpoint inferred from the specified realm. |
|
|
Set the HEC endpoint URL explicitly instead of the endpoint inferred from the specified realm. |
|
|
Set the HEC token if it’s different than the specified Splunk access token. |
|
|
Whether to install and configure fluentd to forward log events to the collector. See Collect Windows logs with Fluentd for more information. |
|
|
Whether to install and configure .NET tracing to forward .NET application traces to the local collector. |
|
|
A system-wide environment tag used by .NET instrumentation. Sets the |
|
|
The location of your Smart Agent bundle for monitor functionality. |
|
|
If true then certificates aren’t checked when downloading resources. |
|
|
Specify a specific version of the Collector to install. |
Latest version available |
|
The package stage to install from [ |
|
|
When installing the Collector, instead of downloading the package, use this local path to a Splunk OpenTelemetry Collector MSI package. If specified, the |
|
|
Specify the URL to the Fluentd MSI package to install. |
|
|
Specify a local path to a Splunk OpenTelemetry Collector MSI package to install instead of downloading the package. If specified, the |
|
|
Specify public MSI properties to be used when installing the Splunk OpenTelemetry Collector MSI package. |
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.