. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1549 3 Process configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . enable profiling • prof_disable - disable profiling Profiling can be enabled per server/proxy process. Enabled profiling provides details of all rwlocks/mutexes by function name. See also: • Zabbix proxy The heartbeat sender has been removed from the proxy. Therefore, Zabbix proxy item zabbix [process,heartbeat sender] is no longer supported and has been removed from templates. The HeartbeatFrequency

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1601 2 3 Process configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 handling - either to frontend locations except the Data collection section. A new configuration syncer worker server process has been added that is responsible for resolving and synchronizing the user macro values in item

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1439 3 Process configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . for trigger expression debugging and internal actions. Expression debugging macros simplify the process of debugging trigger expressions: • {TRIGGER.EXPRESSION.EXPLAIN}, {TRIGGER.EXPRESSION.RECOVERY.EXPLAIN} has been added to Zabbix server and proxy configuration files. You can use internal item zabbix[process,] to monitor ODBC pollers load. Runtime command transfer Zabbix server and proxy runtime

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1460 3 Process configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . return a list of running processes/threads or summarized data grouped by process name. See also: • Zabbix agent item keys • Process parameters returned by proc.get item Extended VMware monitoring Multiple maximum supported version for TimescaleDB is now 2.9. Configuration import Previously, the import process would fail on a UUID mismatch of an importable entity (host group, item, graph, etc). For example

trigger prototypes has been optimized by reducing the number of SQL statements. As a result, the process of creating triggers takes only half of the time as before. 5.10 Multiple OID support in SNMP discovery 1 month as main interval and 15 days as sub-interval * 1 year as main interval and 1/3/4/6 month(s) as sub-intervals * 5 years as main interval and 1 year as sub-interval * 10 years as main interval and * 15 years as main interval and 3 years as sub-interval * 20 years as main interval and 5 years as sub-interval * 30 years as main interval and 10 years as sub-interval * 40 years as main interval and 20

been changed. The possibility of using IP addresses in simple checks has been added. The upgrade process converts all existing simple checks. 5.3.2.3 Ability to send empty strings User parameters, external external checks has been removed and now external check param- eters may be fully customised. Upgrade process adds this macro as a first parameter to all existing external checks. 5.3.2.5 Multi-line value support SNMP, IPMI, JMX - and returns values for available, unavailable and unknown. The database upgrade process doesn’t convert all existing ’status’ keys and associated triggers to the new syntax, so they have

the master item data. See also: Dependent items 5 Parallel processing of alerts A single alerter process was used in the previous versions to send problem notifications. Alerts were sent out one by one In the new version, parallel processing of alerts is implemented. There is a new alert manager process that can distribute alerts to several ”worker” processes, if needed. Media types are processed in Attempts and Retry interval: • Functionality of the database watchdog process has been merged into the alert manager and the watchdog process itself removed. 6 Improved notifications 6.1 Notification on problem

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1333 3 Process configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . a single location. To simplify the navigation Web and Graphs sections have been removed from the main menu in Monitoring. Both sections can now be accessed by clicking on respected links in Monitoring Monitoring → Hosts section. The following information is available from Monitoring → Hosts: • Hostname • Main interface • Availability • Tags • Problems (icons indicating currently open problems) 19 • Status

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1497 3 Process configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . steps or complex logic. As an example, a Script item can be configured to make an HTTP call, then process the data received in the first step in some way, and pass transformed value to the second HTTP call preprocessing step can be used only once and it makes sense to have it as the first preprocessing step. The main use cases for this functionality are as follows: • you may want some items to never go unsupported

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1557 3 Process configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . from the dashboard action menu for the currently opened dashboard. 10 A new Zabbix web service process should be installed to enable generation of scheduled reports. Currently scheduled reports generation (none unavailable) • The zabbix[host,,available] internal item now reports availability of the main interface of a particular type of checks • The logic of counting host availability has also been