zabbix[process,,,] (alerter, db watchdog, escalator, node watcher, proxy poller, timer processes aren’t supported, but two new processes are supported - data sender and heartbeat sender) one operation. 5.25.7 Multiple timer processes Zabbix server daemon will support parallel processing of time-based functions. A user can specify the number of timer processes in the new StartTimers alerts config in 0.018748 sec, idle 60 sec] zabbix22 4608 4584 0 14:55 ? 00:00:00 zabbix_server: timer #1 [processed 3 triggers, 0 events in 0.007867 sec, 0 maint.periods in 0.005677 sec, idle 30 sec]

functions such as nodata(), date(), dayofmonth(), dayofweek(), time() and now() has been moved from timer processes to history syncers. While previously all time-based triggers were recalculated at the same history syncer and timer processes has been updated accordingly. Now: zabbix_server: history syncer #3 [processed 0 values, 0 triggers in 0.000005 sec, idle 1 sec] zabbix_server: timer #1 [updated 0 hosts Before: zabbix_server: history syncer #4 [synced 35 items in 0.166198 sec, idle 5 sec] zabbix_server: timer #1 [processed 3 triggers, 0 events in 0.007867 sec, 0 maint.periods in 0.005677 sec, idle 30 sec]

with time-based functions in the recovery expression only are not periodically recalculated by the timer process. API The output parameter does not work properly with the history.get method. API login SNMP traps task manager - process for manually closing problems (not supported on proxy) timer - process for evaluation of time-related trigger functions and mainte- nances (not supported time(), now()) are used in the expression, the trigger is recalculated every 30 seconds by a Zabbix timer process. If both time-based and non-time-based functions are used in an expression, it is recalculated

process for collecting internal server statistics snmp trapper - trapper for SNMP traps timer - process for evaluation of time-related trigger functions and mainte- nances (not supported time(), now()) are used in the expression, the trigger is recalculated every 30 seconds by a Zabbix timer process. If both time-based and non-time-based functions are used in an expression, it is recalculated mode, Zabbix will send a problem notification. Zabbix server must be running during maintenance. Timer processes are responsible for switching host status to/from mainte- nance at 0 seconds of every minute

one main, history syncer or timer process at a time, which should eliminate problems like multiple successive OK events and might lead to a performance improvement for timer processes on large systems process for collecting internal server statistics snmp trapper - trapper for SNMP traps timer - process for evaluation of time-related trigger functions and mainte- nances trapper - time(), now()) are used in the expression, the trigger is recalculated every 30 seconds by a zabbix timer process. If both time-based and non-time-based functions are used in an expression, it is recalculated

close problem, ac- knowledge problem, check item value now, remote command functional- ity) timer - process for evaluation of time-related trigger functions and mainte- nances (not supported time(), now()) are used in the expression, the trigger is recalculated every 30 seconds by a Zabbix timer process. If both time-based and non-time-based functions are used in an expression, it is recalculated mode, Zabbix will send a problem notification. Zabbix server must be running during maintenance. Timer processes are responsible for switching host status to/from mainte- nance at 0 seconds of every minute

against the database and thus performance improvements. The same improvements also affect the internal timer process (only one such process may run currently), which calculates triggers that include time based time based functions are used in the expression, it is recalculated every 30 seconds by a zabbix timer process. If both time-based and non-time-based functions are used in an expression, it is recalculated statistics poller - normal poller for passive checks proxy poller - poller for passive proxies timer - process for evaluation of time-related trigger functions and maintenances trapper - trapper

process for collecting internal server statistics snmp trapper - trapper for SNMP traps timer - process for evaluation of time-related trigger functions and mainte- nances (not supported time(), now()) are used in the expression, the trigger is recalculated every 30 seconds by a Zabbix timer process. If both time-based and non-time-based functions are used in an expression, it is recalculated mode, Zabbix will send a problem notification. Zabbix server must be running during maintenance. Timer processes are responsible for switching host status to/from mainte- nance at 0 seconds of every minute

close problem, acknowledge problem, check item value now, remote command functionality) • timer - timer for processing maintenances • trapper - trapper for active checks, traps, proxy communication execution by the timeout option (see Plugin.Redis.Timeout configuration parameter); • A special timer closes connections that have not been accessed too long (see Plugin.Redis.KeepAlive configuration manager, preprocess- ing worker, proxy poller, self- monitoring, snmp trapper, task manager, timer, trapper, unreachable poller, vmware collector Supported types of proxy processes: configuration

close problem, acknowledge problem, check item value now, remote command functionality) • timer - timer for processing maintenances • trapper - trapper for active checks, traps, proxy communication manager, preprocess- ing worker, proxy poller, self- monitoring, snmp trapper, task manager, timer, trapper, unreachable poller, vmware collector Supported types of proxy processes: configuration during maintenance. Timer processes are responsible for switching host status to/from maintenance at 0 seconds of every minute. Note that when a host enters maintenance, Zabbix server timer processes will