.NET 6+
Raygun APM profiles modern .NET applications without requiring an application package or source-code instrumentation. For ASP.NET Core, APM 3.1 includes a managed startup hook that gives each request a stable identity across async execution.
Choose your platform
- Install the Agent on Windows, then follow .NET on Windows profiler setup.
- Install the Agent on Linux, then follow .NET on Linux profiler setup.
- For Windows Azure App Service, install the .NET Raygun APM extension.
The current Linux installer supports AMD64 and ARM64 on glibc 2.27 or newer. The Windows installer supports 64-bit Windows Server 2016 or newer and includes both x64 and x86 profilers.
Application configuration
Each profiled application needs:
- its Raygun application API key;
- the native profiler enablement variables and stable profiler path;
- the managed startup hook through
DOTNET_STARTUP_HOOKS; and - a process restart after configuration.
The startup hook observes ASP.NET Core request events without Raygun middleware or application code changes. Raygun's Windows configuration tools and Windows Azure App Service extension add the hook while preserving other startup-hook entries. On Linux, add the hook path printed by the installer to the application environment.
The API key belongs to the application process. Do not place it in the Agent service configuration.
Stop profiling
Remove the profiler and Raygun startup-hook environment from the application, then restart it. On Windows, use the Configuration Utility for IIS application pools or the Agent command line for supported Windows services.
If traces do not appear, use the APM troubleshooting guides.