Get started

To get started with zero-code instrumentation for Windows, follow these steps:

1. Install the package

2. Configure the .NET instrumentation

3. (Optional) Upgrade the package

Install the package

By default, the installer script only installs the Collector. If you add the with_dotnet_instrumentation parameter, the script also downloads and installs the Splunk Distribution of OpenTelemetry .NET.

Run the PowerShell script with the with_dotnet_instrumentation parameter, as shown in the following example:

& {Set-ExecutionPolicy Bypass -Scope Process -Force; `
$script = ((New-Object System.Net.WebClient).DownloadString('https://dl.signalfx.com/splunk-otel-collector.ps1')); `
$params = @{access_token = "<access_token>"; realm = "<realm>"; mode = "agent"; with_dotnet_instrumentation = "`$true"; deployment_env = "<environment_name>"}; `
Invoke-Command -ScriptBlock ([scriptblock]::Create(". {$script} $(&{$args} @params)"))}

Do the following to customize the command:

• Replace <environment_name> with the label for the target environment.

• Replace <access_token> with a valid Splunk Observability Cloud access token. To obtain an access token, see Retrieve and manage user API access tokens using Splunk Observability Cloud.

• Replace <realm> is the Splunk Observability Cloud realm, for example, us0. To find the realm name of your account, open the navigation menu in Splunk Observability Cloud, select Settings, and then select your username. The realm name appears in the Organizations section.

Configure the .NET instrumentation

To configure .NET instrumentation, see Configure the Splunk Distribution of OpenTelemetry .NET.

(Optional) Upgrade the package

You can upgrade the package by installing a new version of the Splunk Distribution of OpenTelemetry .NET. See Instrument your .NET application for Splunk Observability Cloud (OpenTelemetry).

Troubleshooting