filter options won’t reload the item list immediately anymore, thus making filter easier to use on large installations. Also changing most options in item editing form won’t reload it, just the appropriate 10.2.1 Configuration cache reloading 54 Zabbix server and proxy daemons now have an ability to reload in-memory configuration cache upon request. This can be done by passing parameter -R or --runtime-control --runtime-control and a runtime control option. Currently only one runtime option is supported - config_cache_reload. Additional benefit when using active Zabbix proxies is that active proxy will request configuration

bcrypt. Now support of MD5 cryptography has been dropped completely. Reload proxy configuration It is now possible to force the reload of configuration for proxies from the server. It can be done in two two ways: • by Zabbix server runtime control command (e.g. zabbix_server -R proxy_config_cache_reload) • from the frontend (in the list of proxies or the proxy editing form) It is also now possible for 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

proxy_config_cache_reload[=] Reload proxy configuration cache. target - comma-delimited list of proxy names If no target is specified, reload configuration for all proxies secrets_reload Reload secrets runtime control to reload the server configuration cache: shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R config_cache_reload Examples of using runtime control to reload the proxy configuration: configuration: Reload configuration of all proxies: shell> zabbix_server -R proxy_config_cache_reload Reload configuration of Proxy1 and Proxy2: shell> zabbix_server -R proxy_config_cache_reload=Proxy1,Proxy2

proxy_config_cache_reload[=] Reload proxy configuration cache. target - comma-delimited list of proxy names If no target is specified, reload configuration for all proxies secrets_reload Reload secrets to reload the server configuration cache: zabbix_server -c /usr/local/etc/zabbix_server.conf -R config_cache_reload Examples of using runtime control to reload the proxy configuration: # Reload configuration of all proxies: zabbix_server -R proxy_config_cache_reload # Reload configuration of Proxy1 and Proxy2: zabbix_server -R proxy_config_cache_reload=Proxy1,Proxy2 Examples of using runtime control to gather

Processes User parameter reload without agent restart User parameters now can be reloaded from the configuration file without restarting the agent. To do so, run the new userparameter_reload runtime control option option, e. g.: zabbix_agentd -R userparameter_reload or zabbix_agent2 -R userparameter_reload UserParameter is the only agent configuration option that will be reloaded with this command. PCRE2 support The new lock can be write locked only by the configuration syncer performing a configuration cache reload. 24 18 What’s new in Zabbix 6.0.13 Breaking changes Loadable plugin versioning Loadable plugins

required. 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 The new lock can be write locked only by the configuration syncer performing a configuration cache reload. Patch for API queries optimization Optional patches are now available for optimizing API database zabbix_server -V Runtime control Runtime control options: Option Description Target config_cache_reload Reload configuration cache. Ignored if cache is being currently loaded. diaginfo[=] Gather

zabbix_server -V Runtime control Runtime control options: Option Description Target config_cache_reload Reload configuration cache. Ignored if cache is being currently loaded. diaginfo[=] Gather statistics lld - LLD manager statistics locks - list of mutexes secrets_reload Reload secrets from Vault. snmp_cache_reload Reload SNMP cache, clear the SNMP properties (engine time, engine boots, engine specified. Example of using runtime control to reload the server configuration cache: shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R config_cache_reload Examples of using runtime control to gather

zabbix_server -V Runtime control Runtime control options: Option Description Target config_cache_reload Reload configuration cache. Ignored if cache is being currently loaded. diaginfo[=] Gather statistics lld - LLD manager statistics locks - list of mutexes secrets_reload Reload secrets from Vault. snmp_cache_reload Reload SNMP cache, clear the SNMP properties (engine time, engine boots, engine specified. Example of using runtime control to reload the server configuration cache: shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R config_cache_reload Examples of using runtime control to gather

Monitoring → Triggers. Now a string No events will be shown instead. • Page refresh should now reload less files, thus improving overall frontend performance and decreasing the network traffic. • In options: Option Description config_cache_reload Reload configuration cache. Ignored if cache is being currently loaded. Example of using runtime control to reload the server configuration cache: shell> shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R config_cache_reload Process user Zabbix server is designed to run as a non-root user. It will run as whatever non-root user it is started as. So

sound is set to ’Once’. • When Play sound is set to ’Once’ it will not replay the sound on page reload. • In case of several notifications, the sound of the most severe or the most recent notification zabbix_server -V Runtime control Runtime control options: Option Description Target config_cache_reload Reload configuration cache. Ignored if cache is being currently loaded. housekeeper_execute Start the specified. Example of using runtime control to reload the server configuration cache: shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R config_cache_reload Example of using runtime control to trigger