- System requirements
- Profiler architecture
- Profiler installation
- Uninstall profiler
- Running the profiler
- Profiler activation
- Welcome screen
- Start profiling
- Profiling overhead
- Snapshots
- Solving performance problems
- CPU profiling
- Thread profiling
- Object allocation profiling
- Memory profiling
- Exception profiling
- Telemetry
- Probes: monitor higher level events
- Inspections: automatic recognition of typical problems
- Automatically trigger actions on event
- Automatic deobfuscation
- Summary, automatic deobfuscation
- Filters
- Profiler command line
- Command line tool to control profiling
- Export of profiling results to external formats
- Profiler .NET API
- Profiler HTTP API
- Settings
- Troubleshooting
Profiler .NET API
The profiler .NET API allows you to control profiling programmatically right from your .NET application. You can use this API to implement self-monitoring applications, or build complex unit memory tests.
Please find API documentation here
Windows and Linux
The profiler API NuGet package file is located in <Profiler Installation Directory>/api/.
You can use it from there or copy into other location,
see <Profiler Installation Directory>/license-redist.txt for redistribution options.
macOS
The profiler API NuGet package file is located in <Profiler Installation Directory>/Contents/Resources/api/.
Using API
Reference the directory and profiler API package in your project like this:
<PropertyGroup>
<RestoreSources>$(RestoreSources);$(Profiler_Installation_Directory)/api/;</RestoreSources>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="YourKit.Profiler.Api" Version="*"/>
</ItemGroup>
To control profiling programmatically, please also consider HTTP API. Using language neutral tools might be more convenient and simpler in some cases.