.NET¶

To install the .NET Tracer machine-wide:

1. Download the .NET Tracer MSI installer. Select the MSI installer for the architecture that matches the operating system (x64 or x86).

2. Run the .NET Tracer MSI installer with administrator privileges.

You can also script the MSI setup by running the following in PowerShell: Start-Process -Wait msiexec -ArgumentList '/qn /i datadog-apm.msi'

1. Download the latest .NET Tracer MSI package that supports your operating system and architecture.
2. Run one of the following commands to install the package and create the .NET tracer log directory /var/log/datadog/dotnet with the appropriate permissions:

To install the .NET Tracer machine-wide:

** Debian or Ubuntu ** sudo dpkg -i./datadog-dotnet-apm_<TRACER_VERSION>_amd64.deb &&/opt/datadog/createLogPath.sh ** CentOS or Fedora ** sudo rpm -Uvh datadog-dotnet-apm<TRACER_VERSION>-1.x86_64.rpm &&/opt/datadog/createLogPath.sh ** Alpine or other musl-based distributions ** sudo tar -C/opt/datadog -xzf datadog-dotnet-apm-<TRACER_VERSION>-musl.tar.gz && sh/opt/datadog/createLogPath.sh ** Other distributions ** sudo tar -C/opt/datadog -xzf datadog-dotnet-apm<TRACER_VERSION>-tar.gz &&/opt/datadog/createLogPath.sh

1. Use NuGet package to add Datadog.Trace.Bundle to the application.

1. The.NET Tracer MSI installer adds all required environment variables. Other environment variables need to be configured here.
2. To automatically detect applications hosted in IIS, run the following command as an administrator to stop and start IIS completely:

   net stop /y was
   net start w3svc
   

Non-IIS applications

1. Set the following required environment variables for automatic detection to be attached to the application:

   CORECLR_ENABLE_PROFILING=1
   CORECLR_PROFILER={846F5F1C-F9AE-4B07-969E-05C26BC060D8}
   

2. Restart the application.

1. Add environment variables necessary for automatic detection to your application:

   CORECLR_ENABLE_PROFILING=1  
   CORECLR_PROFILER={846F5F1C-F9AE-4B07-969E-05C26BC060D8}  
   CORECLR_PROFILER_PATH=/opt/datadog/Datadog.Trace.ClrProfiler.Native.so  
   DD_DOTNET_TRACER_HOME=/opt/datadog  
   

2. Restart the application

1. In application code, access the global tracker through the Datadog.Trace.Tracer.Instance property to create a new span.

1. Open the Registry Editor, find a multi-string value named HKLM\System\CurrentControlSet\Services\WAS in the registry key, and add environment variables one per line. For example, to add log injection and runtime metrics, add the following lines to the value data:

   DD_LOGS_INJECTION=true
   DD_RUNTIME_METRICS_ENABLED=true
   

2. Run the following command to restart IIS:

   net stop /y was
   net start w3svc
   # Also, start any other services that were stopped when WAS was shut down.
   

   ! Img

1. Create a file named environment.env that contains:

   # Set environment variables
   CORECLR_ENABLE_PROFILING=1
   CORECLR_PROFILER={846F5F1C-F9AE-4B07-969E-05C26BC060D8}
   CORECLR_PROFILER_PATH=/opt/datadog/Datadog.Trace.ClrProfiler.Native.so
   DD_DOTNET_TRACER_HOME=/opt/datadog
   
   # Set additional Datadog environment variables
   DD_LOGS_INJECTION=true
   DD_RUNTIME_METRICS_ENABLED=true
   

2. In the service's configuration file, refer to it as EnvironmentFile in the service block:

   [Service]
   EnvironmentFile=/path/to/environment.env
   ExecStart=<command used to start the application>
   

3. Restart the.NET service.

1. Set the required environment variables by running systemctl-Set-environment

   systemctl set-environment CORECLR_ENABLE_PROFILING=1
   systemctl set-environment CORECLR_PROFILER={846F5F1C-F9AE-4B07-969E-05C26BC060D8}
   systemctl set-environment CORECLR_PROFILER_PATH=/opt/datadog/Datadog.Trace.ClrProfiler.Native.so
   systemctl set-environment DD_DOTNET_TRACER_HOME=/opt/datadog
   
   # Set additional Datadog environment variables
   systemctl set-environment DD_LOGS_INJECTION=true
   systemctl set-environment DD_RUNTIME_METRICS_ENABLED=true
   

2. Run systemctl show environment to verify that the environment variable was successfully set.

3. Restart the application service.