- System requirements
- Profiler architecture
- Running the profiler
- Profiler activation
- Start profiling
- 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 Table
- Profiler events in table 'Messages'
- Event Timeline
- Event Call Tree
- Event stack traces
- Navigation between views
- Events in range
- 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
- 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?
Profiler events in table 'Messages'
Profiler events such as switching profiling modes, starting/stopping profiling, capturing snapshots etc. are logged to the log file, as well to built-in table "Messages" (categories "Profiler" and "Profiler UI").
You can add your own messages in your probes via API
class com.yourkit.probes.builtin.Messages.
You can see "Messages" table in the probes UI:
