- System requirements
- Profiler architecture
- Running the profiler
- Profiler activation
- Start profiling
- IDE integration
- Java server integration wizard
- Attach profiler to a running application
- Attaching from profiler UI
- Console attach wizard
- Remote profiling
- Docker
- Enabling profiling manually
- Startup options
- Connect to profiled application
- Profiling troubleshooting
- Profiling overhead: how to reduce or avoid
- Solving performance problems
- CPU profiling
- Threads
- Deadlock detector
- Memory profiling
- Garbage collection
- Monitor profiling
- Exception profiling
- Probes: monitor events of various kinds
- Performance Charts
- Inspections: automatic recognition of typical problems
- Automatically trigger actions on event
- Summary, snapshot annotation, automatic deobfuscation
- Time measurement (CPU time, wall time)
- Filters
- Snapshot directory customization
- Export of profiling results to HTML, CSV, XML, plain text
- Profiler Java API
- Profiler HTTP API
- Command line tool to control profiling
- Settings
- FAQ: How to profile in my scenario?
Attaching from profiler UI
All detected running Java processes are shown in the Monitor Applications list on Welcome screen. The colored circle indicates the profiler agent status. When agent is already loaded the circle is green. Orange circle shows that agent is not yet loaded but can be attached.
Attach to the application you want to profile by clicking on its name. Attach from context menu to provide custom agent options.
Attaching is possible to both local and remote applications.
Local applications are shown under the node with 
icon.
Applications running on the remote machines are shown under their own nodes with 
icon.
To add a new remote machine click 
.
See remote profiling from user interface
to learn more.
If you do not see your application it the list, please read Profiling troubleshooting. You can use a web browser to check the profiler agent status.