implemented allowing to cache the result of calculated trend functions. Zabbix server, when processing trend functions, will check the trend cache for the cached result. In case of failure the server will will read data from database and cache the result. 13 The trend function cache may help to decrease the database server load when triggers contain trend functions mixed with history or timer-based functions Zabbix server (or proxy) asks for data, for example, CPU load, and Zabbix agent sends back the result. Active checks require more complex processing. The agent must first retrieve a list of items from

values for period • trendsum - sum of trend values for period Note that the new functions return a result based on trend values, not history. For example, you may want to know if there was a significant Zabbix server (or proxy) asks for data, for example, CPU load, and Zabbix agent sends back the result. Active checks require more complex processing. The agent must first retrieve a list of items from embedded script testing. This utility will execute a user script with a string parameter and print the result. Scripts are executed using the embedded Zabbix scripting engine. In case of compilation or execution

Zabbix server (or proxy) asks for data, for example, CPU load, and Zabbix agent sends back the result. 26 Active checks require more complex processing. The agent must first retrieve a list of items embedded script testing. This utility will execute a user script with a string parameter and print the result. Scripts are executed using the embedded Zabbix scripting engine. In case of compilation or execution All tests successful. Files=152, Tests=1152, 501 wallclock secs ( 0.67 usr + 0.61 sys = 1.28 CPU) Result: PASS e:\openssl-1.1.1> nmake install_sw’install_sw’ installs only software components (i.e. libraries

configuration file (zabbix.conf.php) in the following manner: GUI settings Configuration file Description Result ... // Used for TLS connection. $DB[’ENCRYPTION’] = true; $DB[’KEY_FILE’] = ”; $DB[’CERT_FILE’] certificate unchecked Enable ’required’ mode. 18 GUI settings Configuration file Description Result ... $DB[’ENCRYPTION’] = true;\\ $DB[’KEY_FILE’] = ”; $DB[’CERT_FILE’] = ”; $DB[’CA_FILE’] = the respective parameters in the Zabbix server and/or proxy configu- ration file. Configuration Result None Connection to the database without encryption. 1. Set DBTLSConnect=required Server/proxy

functionality gap in the new version, rate() and histogram_quantile() functions, producing the same result as their PromQL counterparts, have been added. Other new additions to complement this functionality string. Result processing for Prometheus pattern A Prometheus pattern step in the preprocessing can produce a result where multiple lines are matched. To handle this situation, a new result processing records about all configuration changes for all Zabbix objects, including changes that occurred as a result of executing an LLD rule, a network discovery action, an autoregistration action, or a script execution

SNMP versions 2/3. A GetBulk request in SNMP executes multiple GetNext requests and returns the result in a single response. Previously, only the SNMP discovery[] item in Zabbix would use GetBulk requests; cases when a proxy would constantly receive data older than set in ProxyOfflineBuffer, this could result in excessive data accumulation. Now this limitation has been removed, providing a more effective Zabbix server (or proxy) asks for data, for example, CPU load, and Zabbix agent sends back the result. Active checks require more complex processing. The agent must first retrieve a list of items from

scenario steps. For example: Version Variable syntax Result Before 3.4 {user} Variable value is passed as is. 12 Version Variable syntax Result In 3.4 {user} {user} {{user}.urlencode()} {{user} have been added (>= and <=); • The constant field is now combined with the operator field and named Result. 19 What’s new in Zabbix 3.4.14 Item changes • system.cpu.num agent item on AIX now returns the Zabbix server (or proxy) asks for data, for example, CPU load, and Zabbix agent sends back the result. Active checks require more complex processing. The agent must first retrieve a list of items from

executed steps, reporting on the result or failure of each preprocessing step. Preprocessing failed for: 1. Result (): 2. Result (): Expected format change in low-level discovery In order to support preprocessing of low-level discovery result and custom paths to low-level discovery (LLD) macro values in a JSON document, the format of JSON configuration has gained additional options of preprocessing the discovery result and extracting custom macros from the preprocessed result. To better understand the changes in the discovery data flow, let’s

candidate, 4 - release) • {nn} - sequence number for the ’type’ For example: Tag Branch Version Result 4.0.8 Zabbix 4.0.8 4.0.8.2400 release/4.0 Zabbix 4.0.8rc3 4.0.8.1303 feature/ZBX-16074 Zabbix discovery VMware datastore discovery has been moved from hypervisor level to vCenter level. As a result datastores are discovered and datastore info is collected only once for each datastore instead of to mark this checkbox a warning message is displayed that all inherited entities may be lost as a result. 22 What’s new in Zabbix 4.0.17 New items A new vfs.fs.get agent item has been added that returns

to mark this checkbox a warning message is displayed that all inherited entities may be lost as a result. Zabbix agent 2 (Windows) Zabbix agent 2 can now be compiled from sources on the Windows platform Zabbix server (or proxy) asks for data, for example, CPU load, and Zabbix agent sends back the result. Active checks require more complex processing. The agent must first retrieve a list of items from implement one or several plugin interfaces. func (p *Plugin) Export(key string, params []string) (result interface{}, err error) { if len(params) > 0 { p.Debugf("received %d parameters while expected none"