- System requirements
- Profiler architecture
- Profiler installation
- Uninstall profiler
- Running the profiler
- Profiler activation
- Welcome screen
- Start profiling
- IDE integration
- Java server integration wizard
- Attach profiler to a running application
- Remote profiling
- Profiling in Docker container
- Profiling in Docker container using port forwarding
- Profiling in Docker container using YourKit Connection Broker
- Profiling in Amazon EC2 instance
- Enabling profiling manually
- Startup options
- Connect to profiled application
- Profiling overhead
- Snapshots
- Solving performance problems
- CPU profiling
- Thread profiling
- Virtual threads support
- Memory profiling
- Object allocation profiling
- Garbage collection
- Monitor profiling
- Exception profiling
- Telemetry
- Probes: monitor events of various kinds
- Inspections: automatic recognition of typical problems
- Automatically trigger actions on event
- Automatic deobfuscation
- Summary
- Filters
- Profiler command line
- Export of profiling results to external formats
- Profiler Java API
- Profiler HTTP API
- Settings
- Troubleshooting and FAQ
Profiling in Docker container
Profiling Java 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 Java 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.