Zabbix Active & Discovery

This example assumes that Template_Zorka_JVM_Active template is present. If not, please import it from templates/zbx34 directory.

Agent side

The following things must be set in zorka.properties:

• zabbix.active = yes - to enable active agent;
• zabbix.server.addr - address of zabbix server (use zabbix.active.server.addr if address differs from standardzabbix protocol communication);
• zorka.hostname - host used to register agent (must be unique);
• zabbix.active.host.metadata - set some secure key and ZORKA_JVM keyword, for example:

zabbix.active.host.metadata = 1qaz2wsx3edc4rfv5tgb ZORKA_JVM

Zabbix side

• go to Configuration->Actions screen and select Auto registration as event source;
• click Create action to open new rule;
• add new condition of type Host metadata containing key entered to zabbix.active.host.metadata of agent configuration;
• add new condition of type Host metadata containing ZORKA_JVM word;
• change Type of calculation value to Add;
• switch to Operations tab;
• add new Add host operation;
• add new Link to template operation, select Template_Zorka_JVM_Active template;

Active checks related options

• zabbix.active = no - enables zabbix active agent;
• zabbix.active.batch.size = 10 - maximum number of metrics sent every sender cycle;
• zabbix.active.cache.size = 150 - maximum number of collected metrics awaiting to be sent to zabbix server;
• zabbix.active.check.interval = 120 - defines how often agent will query zabbix server for metrics to check;
• zabbix.active.message.size = 16384 - maximum size of data messages sent to zabbix server;
• zabbix.active.sender.interval = 60 - defines how often collected metrics will be sent sent to zabbix server;
• zabbix.active.server.addr = ${zabbix.server.addr} - zabbix server address for handling active requests;typically this is the same as zabbix.server.addr, so no need for changing this setting in most cases;