- Running the profiler
- Profiler activation
- Running applications with the profiler
- Connect to profiled application
- Troubleshoot connection problems
- Solving performance problems
- CPU profiling
- Threads
- Deadlock detector
- Memory profiling
- Garbage collection
- Monitor profiling
- Exception profiling
- Probes: monitor events of various kinds
- Events in user interface
- Event inspections
- Built-in probes
- Probe classes
- Monitoring method invocation events
- Data storage
- Performance Charts
- Inspections: automatic recognition of typical problems
- Automatically trigger actions on event
- Summary, snapshot annotation, automatic deobfuscation
- IDE integration
- Time measurement (CPU time, wall time)
- Filters
- Snapshot directory customization
- Export of profiling results to HTML, CSV, XML, plain text
- Profiler API
- Command line tool to control profiling
- FAQ: How to profile in my scenario?
Probe classes
Probe class is a Java class intended to monitor execution of particular methods.
Bytecode instrumentation engine will inject calls to your probes to the methods which you specified.
You can access method parameters, method return value, the object for which the method is called, as well as intercept uncaught exceptions thrown in the method.
This provides virtually unlimited capabilities to monitor applications. Read more...
Probe life cycle
- Write the probe class(es)
- Compile the probe class(es)
- Register the probe class(es) to make them work
- (Optional) To deactivate the probe in runtime, unregister its class(es)