- System requirements
- Profiler architecture
- Profiler installation
- Uninstall profiler
- Running the profiler
- Profiler activation
- Welcome screen
- Start profiling
- IDE integration
- Profile .NET executable
- Profile ASP.NET application in IIS
- Profile ASP.NET web app on Azure App Service on Linux
- Profile ASP.NET web app on Azure App Service on Windows
- Profile all .NET processes that will start
- Attach profiler to a running application
- Profile remote applications
- Profiling in Docker container
- Profiling in Docker container using port forwarding
- Profiling in Docker container using YourKit Connection Broker
- Manually enable profiling of local applications
- Startup options
- Connect to profiled application
- Profiling overhead
- Snapshots
- Solving performance problems
- CPU profiling
- Thread profiling
- Memory profiling
- Garbage collection
- 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
Profiling in Docker container
Profiling .NET applications in Docker containers can be challenging due to the restrictive nature of the Docker environment. One of the common issues that developers encounter is setting up communication between the profiler and the .NET application running inside the Docker container.
Port forwarding
This article describes how to set up Docker port forwarding to expose the profiler agent port outside the Docker container. This configuration allows the profiler to connect directly (or through an SSH tunnel) to the profiling agent.
YourKit Connection Broker
This article demonstrates how to profile an application inside a Docker container using YourKit Connection Broker. With this approach, you won't need to open ports or know the IP address of your Docker container.