platforms, written in C) and the Zabbix agent 2 (extra-flexible, easily extendable with plugins, written in Go). Data flow In addition it is important to take a step back and have a look at the overall data flow the configuration file without restarting the agent. To do so, run the new userparameter_reload runtime control option, e. g.: zabbix_agentd -R userparameter_reload or zabbix_agent2 -R userparameter_reload pollers load. Runtime command transfer Zabbix server and proxy runtime commands are now sent via socket instead of Unix signals. This change allowed to improve user experience working with runtime control

platforms, written in C) and the Zabbix agent 2 (extra-flexible, easily extendable with plugins, written in Go). Data flow In addition it is important to take a step back and have a look at the overall data flow Manual SNMP cache clearing Zabbix server and Zabbix proxy now support an -R snmp_cache_reload runtime control option, which reloads the SNMP cache 16 and clears the SNMP properties (engine time, engine displayed when mass updating items. Mutex section added to diagnostic information The ’diaginfo’ runtime control option for server/proxy now also returns a section with Zabbix mutexes. You may also run

platforms, written in C) and the Zabbix agent 2 (extra-flexible, easily extendable with plugins, written in Go). Data flow In addition it is important to take a step back and have a look at the overall data flow mandatory. Also, it is now possible to select a ”None” option in the interface field. Runtime commands for profiling 13 Runtime commands for profiling have been added to Zabbix server and Zabbix proxy. • prof_enable provides details of all rwlocks/mutexes by function name. See also: • Zabbix server runtime commands • Zabbix proxy runtime commands Date removed from export When exporting objects (hosts, templates, etc

define dependencies has now been implemented for trigger prototypes as well. To define dependencies you go to the Dependencies tab in the trigger prototype form (similarly as for real triggers). A trigger a new option in host and template configuration forms with macro resolution details. To see it you go to the Macros tab and select the Inherited and host macros option. That is where all defined user now displayed as buttons. The previous option of a dropdown selection and then having to click on Go has been removed. It is expected that reinstating buttons will make it much quicker and easier to use

that it supports all the previous functionality) Agent 2 is written in Go (with some C code of Zabbix agent reused). A configured Go version 1.12+ environment is required for building Zabbix agent 2. Zabbix is used to ”evaluate” data received in items. When received data are above the threshold, triggers go from ’Ok’ into a ’Problem’ state. When received data are below the threshold, triggers stay in/return Zabbix server in foreground -R --runtime-control perform administrative functions -h --help give this help -V --version display version number Note: Runtime control is not supported on OpenBSD

platforms, written in C) and the Zabbix agent 2 (extra-flexible, easily extendable with plugins, written in Go). Data flow In addition it is important to take a step back and have a look at the overall data flow step. The main use cases for this functionality are as follows: • you may want some items to never go unsupported, for example, in case of transient problems • you may want to be notified when checking is used to ”evaluate” data received in items. When received data are above the threshold, triggers go from ’Ok’ into a ’Problem’ state. When received data are below the threshold, triggers stay in/return

platforms, written in C) and the Zabbix agent 2 (extra-flexible, easily extendable with plugins, written in Go). Data flow In addition it is important to take a step back and have a look at the overall data flow value (and thus it becoming unsupported) previously lacked the ability to distinguish the reason or runtime stage where the process failed. All errors had to be handled using one and the same option for error is used to ”evaluate” data received in items. When received data are above the threshold, triggers go from ’Ok’ into a ’Problem’ state. When received data are below the threshold, triggers stay in/return

of a special ”Recovery message” or the possibility to create a full escalation when problem triggers go OK, now that has been united into one ”Recovery operation” concept. In a recovery operation you can /usr/local/etc/zabbix_server.conf) -R --runtime-control perform administrative functions -h --help give this help -V --version display version number Note: Runtime control is not supported on OpenBSD -c /usr/local/etc/zabbix_server.conf shell> zabbix_server --help shell> zabbix_server -V Runtime control Runtime control options: Option Description Target config_cache_reload Reload configuration cache

is used to ”evaluate” data received in items. When received data are above the threshold, triggers go from ’Ok’ into a ’Problem’ state. When received data are below the threshold, triggers stay in/return /usr/local/etc/zabbix_server.conf) -R --runtime-control perform administrative functions -h --help give this help -V --version display version number Note: Runtime control is not supported on OpenBSD -c /usr/local/etc/zabbix_server.conf shell> zabbix_server --help shell> zabbix_server -V Runtime control Runtime control options: Option Description Target config_cache_reload Reload configuration cache

platforms, written in C) and the Zabbix agent 2 (extra-flexible, easily extendable with plugins, written in Go). Data flow In addition it is important to take a step back and have a look at the overall data flow reload of configuration for proxies from the server. It can be done in two ways: • by Zabbix server runtime control command (e.g. zabbix_server -R proxy_config_cache_reload) • from the frontend (in the list for passive proxies to request configuration from the server using the config_cache_reload proxy runtime control command. Separate groups for templates Previously, host groups were used to organize both