The following settings are recognized by agent:
zorka.mbs.autoregister = yes- this setting controls whether standard platform mbean server should be automaticallyregistered at startup time; if this has been set toyes,jvm.bshscript will get reference to platform mbean serverand register it in aget asjava; if this has been set tono, then mbean server registration will be delegated toapplication server specific script (eg.jboss.bsh); this mechanism is needed as agent initializes before applicationservermain()method is called and some applications expect platform mbean server to be in uninitialized state,so it cannot be referenced at agent startup;zorka.hostname = myapp.myhost- 'hostname' this agent will advertise itself; this is useful for for automaticinforming operating system about server hostname (eg. standard Zabbix Agent template has such item);
Directives useful for tuning (you propably don't need to change default values):
zorka.req.threads = 4- number of threads for processing requests;zorka.req.queue = 64-zorka.req.timeout = 10000- request timeout (in milliseconds) - requests taking more than this will be canceledand zorka will close connection abruply;
General settings regarding
JVM monitoring
jvm.hiccup = yes- enables or disables JVM hiccup metric monitoring; this metric measures JVM pauses; pauses can be caused by various components of JVM (notably garbage collector) or by OS/hypervisor;jvm.hiccup.mbean = zorka:type=ZorkaStats,name=Hiccup- object name of an mbean via which hiccups will be reported;
Zorka internal diagnostics settings
Zorka agent comes with its own built in diagnostics mbean that is collecting parameters regarding agent itself.
zorka.diagnostics = yes- enables or disables zorka diagnostics;zorka.diagnostics.mbean = zorka:type=ZorkaStats,name=Diagnostic- object name of diagnostics mbean;