increased system requirements: • Support for PHP 4 dropped. • Maximal PHP memory size should be at least 128MB (option memory_limit). • Maximal PHP POST size should be at least 16MB (option post_max_size) a true localised or multilanguage setup. 2.3 Improved time period navigation In Zabbix, single control is used to select time period displayed for many views, including simple and custom graphs, raw start/end time. Notice the dynamic/fixed link in the lower right hand corner? It can be used to control whether time period is kept constant when you change start/end time. In addition to the screenshots

be deployed on both Linux and Windows Binary daemons • written in C, for performance and small memory footprint • easily portable Ready for complex environments • remote monitoring made easy by using value type (character, log or text). ** Log level change at runtime ** Two additional runtime control options have been added on all Zabbix services - log_level_increase and log_level_decrease. Now, change the log level of all or certain process(-es) without restarting a service. These two runtime control options accept parameters for target process selection. A target process can be selected by specifying

be deployed on both Linux and Windows Binary daemons • written in C, for performance and small memory footprint • easily portable Ready for complex environments • remote monitoring made easy by using been removed. 5.20 Daemon improvements 5.20.1 Forced housekeeper execution An additional runtime control option (housekeeper_execute) has been added to Zabbix server and Zabbix proxy to support manual DebugLevel=5 in server, proxy and agent configuration files. Previously it could be done using runtime control options only. • A new LogType configuration parameter has been added for server, proxy, agent and

be deployed on both Linux and Windows Binary daemons • written in C, for performance and small memory footprint • easily portable Ready for complex environments • remote monitoring made easy by using Reports → Action log for alerts, when rolling the mouse over the error icon. • Semaphore and shared memory management has been reworked to eliminate the possibility of IPC-related conflicts in between Zabbix disk - process in uninterruptible disk sleep (usually I/O) • trace - process is stopped by job control signal A new zabbix[host,discovery,interfaces] internal item has been added to return all host interfaces

be deployed on both Linux and Windows Binary daemons • written in C, for performance and small memory footprint • easily portable Ready for complex environments • remote monitoring made easy by using conditions that have to be met for the trigger to return back to the OK state. 10 There is also more control over how OK events are generated. You can use the problem expression as basis (then it works the monitor virtual memory statistics on Windows. 7.5.3 Chassis information Changed system.hw.chassis key to read the DMI table from sysfs, if sysfs access fails then try reading directly from memory. 7.6 Trigger

be deployed on both Linux and Windows Binary daemons • written in C, for performance and small memory footprint • easily portable Ready for complex environments • remote monitoring made easy by using 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 boots 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 ’diaginfo’

be deployed on both Linux and Windows Binary daemons • written in C, for performance and small memory footprint • easily portable Ready for complex environments • remote monitoring made easy by using See also: Storage of secrets 9 User roles It is now possible to define user roles for granular control on what parts of UI, which API methods, and which function- ality (such as the ability to acknowledge perf[,] • vmware.vm.guest.memory.size.swapped[,] • vmware.vm.guest.osuptime[,] • vmware.vm.memory.size.consumed[,] • vmware.vm.memory.usage[,] • vmware

be deployed on both Linux and Windows Binary daemons • written in C, for performance and small memory footprint • easily portable Ready for complex environments • remote monitoring made easy by using 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 socket instead of Unix signals. This change allowed to improve user experience working with runtime control options: • Results of the command execution are now printed to the console. • It is possible to

be deployed on both Linux and Windows Binary daemons • written in C, for performance and small memory footprint • easily portable Ready for complex environments • remote monitoring made easy by using 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 of proxies 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 hosts

be deployed on both Linux and Windows Binary daemons • written in C, for performance and small memory footprint • easily portable Ready for complex environments • remote monitoring made easy by using (default is still all and returns normal load value) vm.memory.size now supports more modes for various platforms. See supported by platform and vm.memory.size parameters pages for more information. 5.3.2 Note that monitoring a large amount of disks will increase the memory usage. • Previously, Zabbix agents allocated a static amount of memory for monitoring 8 disks or partitions. This amount is now dynamic