.NET¶

To install the .NET Tracer at the machine level, follow these steps:

1. Download the .NET Tracer MSI installer. Select the MSI installer that matches the architecture of your operating system (x64 or x86).
2. Run the .NET Tracer MSI installer with administrator privileges. You can also script the MSI installer by running the following command in PowerShell: Start-Process -Wait msiexec -ArgumentList '/qn /i datadog-apm.msi'.

To install the .NET Tracer at the machine level, follow these steps:

1. Download the .NET Tracer MSI installer. Select the MSI installer that matches the architecture of your operating system (x64 or x86).
2. Depending on your operating system, run the relevant package with appropriate permissions and create the directory for .NET tracer logs /var/log/datadog/dotnet:

   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

Add .NET Tracer to your application

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

Internet Information Services (IIS):

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

   net stop /y was
   net start w3svc
   

Non-IIS Applications

1. Set the following required environment variables for auto-detection to attach to your application:

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

2. Restart the application.

1. Add the required environment variables for auto-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

Add custom probes to .NET applications:

1. In your application code, access the global tracer via the Datadog.Trace.Tracer.Instance property to create new spans.

After installing the MSI, automatic detection of IIS sites requires no additional configuration. To set additional environment variables inherited by all IIS sites, follow these steps:

1. Open the registry editor, find the multi-string value named Environment under the registry item HKLM\System\CurrentControlSet\Services\WAS, and then 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 commands to restart IIS:

   net stop /y was
   net start w3svc
   # Additionally, any other services stopped when WAS shuts down have been restarted.
   

   

To automatically detect console applications, set environment variables from a batch file before starting the application:

rem Set environment variables
SET CORECLR_ENABLE_PROFILING=1
rem Unless v2.14.0+ and you installed the tracer with the MSI
SET CORECLR_PROFILER={846F5F1C-F9AE-4B07-969E-05C26BC060D8}

rem Set additional Datadog environment variables
SET DD_LOGS_INJECTION=true
SET DD_RUNTIME_METRICS_ENABLED=true

rem Start application
dotnet.exe example.dll

Before starting the application, set the required environment variables from bash:

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

# Set additional Datadog environment variables
export DD_LOGS_INJECTION=true
export DD_RUNTIME_METRICS_ENABLED=true

# Start your application
dotnet example.dll

Configure environment variables in the Docker container:

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

# Set additional Datadog environment variables
ENV DD_LOGS_INJECTION=true
ENV DD_RUNTIME_METRICS_ENABLED=true

# Start your application
CMD ["dotnet", "example.dll"]

When running a .NET application as a service using systemctl, you can add the required environment variables to load for a specific service.

1. Create a file named environment.env containing:

   # 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. Reference it as EnvironmentFile in the service block of the service's configuration file:

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

3. Restart the .NET service.

When running .NET applications as services using systemctl, you can also set environment variables to load for all services run by systemctl.

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 variables have been set successfully.

3. Restart the application service.