Available from 1.90.7-SNAPSHOT.
Thread monitoring enables monitoring thread utilization and logging potentially contentious parts of code. It periodically scans all threads and monitors CPU utilization of all threads. It also periodically dumps most contentious threads.
The following configuration properties in zorka.properties are available:
jvm.thread.monitor = no- enables or disables thread monitor;jvm.thread.monitor.interval = 10000- interval between thread monitor sampling runs.
Thread dumper - CPU contention monitoring
Thread CPU contention monitoring periodically checks for most contentious threads and logs their stack traces for further analysis. Contention monitoring must be explicitly enabled by setting jvm.thread.dumper = yes property.
jvm.thread.dumper = no- enables or disables thread dumper;jvm.thread.dumper.log.path = ${zorka.log.dir}/thread-dumps.log- path to log file where thread dumper stores its logs;jvm.thread.dumper.log.num = 4- number of archived thread dumper log files;jvm.thread.dumper.log.size = 4M- maximum size of single thread dumper log file;jvm.thread.dumper.thr.max = 4- maximum number of threads per dump;jvm.thread.dumper.thread.cpu.min = 30- minimum CPU utilization of a thread to be dumped;jvm.thread.dumper.total.cpu.min = 100- minimum CPU utilization of all threads in order to activate thread dump mechanism;jvm.thread.dumper.stack.depth = 8- maximum number of stack trace items logger for each dumped thread;