Docs » Get started with the Splunk Distribution of the OpenTelemetry Collector » Splunk OpenTelemetry Zero Configuration Auto Instrumentation » Splunk OpenTelemetry Zero Configuration Auto Instrumentation for .NET

Caution

Preview: Splunk Zero Config Auto Instrumentation

Preview features described in this document are provided by Splunk to you “as is” without any warranties, maintenance and support, or service-level commitments. Splunk makes this preview feature available in its sole discretion and may discontinue it at any time. Use of preview features is subject to the Splunk General Terms.

Splunk OpenTelemetry Zero Configuration Auto Instrumentation for .NET 🔗

Splunk OpenTelemetry Zero Configuration Auto Instrumentation for .NET provides a package that automatically instruments your local ASP.NET applications to capture and report distributed traces to the Splunk Distribution of OpenTelemetry Collector, and then on to Splunk APM.

The Zero Configuration package provides the following benefits:

  • You can start streaming traces and monitor distributed applications with Splunk APM in minutes.

  • You don’t need to configure or instrument your .NET back-end services or applications before deployment.

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 SignalFx Instrumentation for .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 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 Observability Cloud realm, for example, us0. To find the realm name of your account, open the left navigation menu in Observability Cloud, select Settings, and then select your username. The realm name appears in the Organizations section.

Configure the .NET instrumentation 🔗

To configure the instrumentation, see Configure the SignalFx Instrumentation for .NET.

Upgrade the package 🔗

You can upgrade the package by installing a new version of the SignalFx Instrumentation for .NET. See Instrument a .NET application for Splunk Observability Cloud.

Report an issue 🔗

Before you create an issue or open a support request, try gathering the following information:

  • What happened and the impact of the issue.

  • All the steps you’ve followed until the issue appeared.

  • What was the expected outcome.

  • Your attempts to solve the issue, including workarounds.

  • The operating system, runtime or compiler version, libraries, frameworks, and application servers of your environment, including your instrumentation settings.

  • Debug logs and other logs that might help troubleshoot the issue.

To get help, see Splunk Observability Cloud support.