Deploy the Collector for Windows with Chef đź”—
Chef is a configuration management technology used to manage infrastructure on physical or virtual machines. Chef uses cookbooks to define a scenario.
Cookbooks are fundamental working units of Chef, which consists of all the details related to working units, having the capability to modify configuration and the state of any system configured as a node on Chef infrastructure. Cookbooks can run multiple tasks.
Prerequisites đź”—
You need the following resources to use Chef:
Double-check exposed ports to make sure your environment doesn’t have conflicts. You can change ports in the Collector configuration. See Exposed ports and endpoints for more information.
Windows đź”—
The following Windows versions. All versions require using PowerShell 3.0 or newer.
Windows Server 2019 64-bit
Windows Server 2022 64-bit
Caution
On Windows, the Collector is installed as a Windows service and its environment variables are set at the service scope, so they’re only available to the Collector service and not to the entire machine.
Install and use the Collector with Chef đź”—
Download the Chef cookbook from the Chef Supermarket , which is the site for community cookbooks.
To install the Collector, include the splunk_otel_collector::default
recipe in the run_list
, and set the attributes on the node’s run_state
. The following is an example configuration that shows how to configure the required splunk_access_token
attribute and some optional attributes:
{
"splunk-otel-collector": {
"splunk_access_token": "<SPLUNK_ACCESS_TOKEN>",
"splunk_realm": "<SPLUNK_REALM>",
}
}
Configure automatic discovery for SignalFx .NET đź”—
You can automatically instrument your .NET applications along with the Collector installation using automatic discovery. Automatic discovery removes the need to install and configure the SignalFx .NET agent separately. See Discover telemetry sources automatically for more information.
The cookbook accepts the attributes described in the following table:
Name |
Description |
Default value |
---|---|---|
|
Whether to install or manage automatic discovery for .NET. When set to |
|
|
Version of the |
|
|
Specify the URL to download the MSI from a custom host, for example |
|
|
By default, the |
|
|
Whether to configure automatic discovery for all .NET applications on the node. When set to |
|
|
Sets the deployment environment variable that is reported to Splunk APM, for example |
|
|
Sets the service name for the instrumented application, for example, |
|
|
Activates or deactivates AlwaysOn Profiling. The value will be assigned to the |
|
|
Activates or deactivates AlwaysOn Memory Profiling. The value will be assigned to the |
|
|
Hash of additional options to be added to the Windows registry in addition to the options above. To learn more, see Configure the SignalFx Instrumentation for .NET. |
|
Additional environment variables đź”—
Use collector_additional_env_vars
to include any additional environment variables from the Collector configuration file for the Collector’s service. {}
by default.
For example, if the Collector’s configuration file includes references to ${MY_CUSTOM_VAR1}
and ${MY_CUSTOM_VAR2}
, specify the following to allow the Collector service to expand these variables:
collector_additional_env_vars: {'MY_CUSTOM_VAR1' => 'value1', 'MY_CUSTOM_VAR2' => 'value2'}
On Linux, the variables/values will be added to the /etc/otel/collector/splunk-otel-collector.conf
systemd environment file.
On Windows, the variables/values will be added to the Environment value under the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\splunk-otel-collector
registry key.
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.