Zero-code instrumentation for back-end applications in Windows 🔗
Automatic discovery for OpenTelemetry .NET activates zero-code instrumentation for .NET applications running on Windows. By default, zero-code instrumentation is only turned on for IIS applications. To activate other application and service types, see Install the Splunk Distribution of OpenTelemetry .NET manually. After installing the package, you must start or restart any .NET applications that you want to instrument.
Note
The SignalFx instrumentation for .NET is deprecated and will reach end of support on February 21, 2025. To learn how to migrate from SignalFx .NET to OpenTelemetry .NET, see Migrate from the SignalFx .NET Instrumentation.
Get started 🔗
To get started with zero-code instrumentation for Windows, follow these steps:
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 , 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 🔗
If you are a Splunk Observability Cloud customer and are not able to see your data in Splunk Observability Cloud, you can get help in the following ways.
Available to Splunk Observability Cloud customers
Submit a case in the Splunk Support Portal .
Contact Splunk Support .
Available to prospective customers and free trial users
Ask a question and get answers through community support at Splunk Answers .
Join the Splunk #observability user group Slack channel to communicate with customers, partners, and Splunk employees worldwide. To join, see Chat groups in the Get Started with Splunk Community manual.