Zabbix Documentation 3.4

2.23.04.04.2 (current)In development:4.4 (devel)Unsupported:1.82.02.43.23.4

User Tools

Site Tools


manual:config:items:itemtypes:internal

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
manual:config:items:itemtypes:internal [2018/06/28 07:19]
martins-v some rewording
manual:config:items:itemtypes:internal [2018/11/07 07:04] (current)
martins-v preprocessing is only supported on server
Line 73: Line 73:
 | |||||| | ||||||
 ^zabbix[process,<​type>,<​mode>,<​state>​] ​ |||||| ^zabbix[process,<​type>,<​mode>,<​state>​] ​ ||||||
-^ |Time a particular Zabbix process or a group of processes (identified by <​type>​ and <​mode>​) spent in <​state>​ in percentage. It is calculated for the last minute only.\\ \\ If <​mode>​ is Zabbix process number that is not running (for example, with 5 pollers running <​mode>​ is specified to be 6), such an item will turn into unsupported state.\\ Minimum and maximum refers to the usage percentage for a single process. So if in a group of 3 pollers usage percentages per process were 2, 18 and 66, min would return 2 and max would return 66.\\ Processes report what they are doing in shared memory and the self-monitoring process summarizes that data each second. State changes (busy/idle) are registered upon change - thus a process that becomes busy registers as such and doesn'​t change or update the state until it becomes idle. This ensures that even fully hung processes will be correctly registered as 100% busy.\\ Currently, "​busy"​ means "not sleeping",​ but in the future additional states might be introduced - waiting for locks, performing database queries, etc.\\ On Linux and most other systems, resolution is 1/100 of a second.|||Percentage of time.\\ Float. |The following process types are currently supported:​\\ **alerter** - process for sending notifications //(not supported on proxy)// ​\\ **alert manager** - manager of alerter tasks\\ **configuration syncer** - process for managing in-memory cache of configuration data\\ **data sender** - proxy data sender //(not supported on server)//\\ **discoverer** - process for discovery of devices\\ **escalator** - process for escalation of actions //(not supported on proxy)//\\ **heartbeat sender** - proxy heartbeat sender //(not supported on server)//\\ **history syncer** - history DB writer\\ **housekeeper** - process for removal of old historical data\\ **http poller** - web monitoring poller\\ **icmp pinger** - poller for icmpping checks\\ **ipmi manager** - IPMI poller manager\\ **ipmi poller** - poller for IPMI checks\\ **java poller** - poller for Java checks\\ **poller** - normal poller for passive checks\\ **preprocessing manager** - manager of preprocessing tasks\\ **preprocessing worker** - process for data preprocessing\\ **proxy poller** - poller for passive proxies //(not supported on proxy)//\\ **self-monitoring** - process for collecting internal server statistics\\ **snmp trapper** - trapper for SNMP traps\\ **task manager** - process for remote execution of tasks requested by other components (e.g. close problem, acknowledge problem, check item value now, remote command functionality)\\ **timer** - process for evaluation of time-related trigger functions and maintenances //(not supported on proxy)//\\ **trapper** - trapper for active checks, traps, proxy communication\\ **unreachable poller** - poller for unreachable devices\\ **vmware collector** - VMware data collector responsible for data gathering from VMware services\\ \\ Note: You can also see these process types in a server log file.\\ \\ Valid modes are:\\ **avg** - average value for all processes of a given type (default)\\ **count** - returns number of forks for a given process type, **<​state>​** should not be specified\\ **max** - maximum value\\ **min** - minimum value\\ **<​process number>​** - process number (between 1 and the number of pre-forked instances). For example, if 4 trappers are running, the value is between 1 and 4.\\ \\ Valid states are:\\ **busy** - process is in busy state, for example, processing request (default).\\ **idle** - process is in idle state doing nothing.\\ \\ Examples:\\ => zabbix[process,​poller,​avg,​busy] -> average time of poller processes spent doing something during the last minute\\ => %%zabbix[process,"​icmp pinger",​max,​busy]%% -> maximum time spent doing something by any ICMP pinger process during the last minute\\ => %%zabbix[process,"​history syncer",​2,​busy]%% -> time spent doing something by history syncer number 2 during the last minute\\ => zabbix[process,​trapper,​count] -> amount of currently running trapper processes\\ \\ This item is supported starting with Zabbix **1.8.5.** ​ |+^ |Time a particular Zabbix process or a group of processes (identified by <​type>​ and <​mode>​) spent in <​state>​ in percentage. It is calculated for the last minute only.\\ \\ If <​mode>​ is Zabbix process number that is not running (for example, with 5 pollers running <​mode>​ is specified to be 6), such an item will turn into unsupported state.\\ Minimum and maximum refers to the usage percentage for a single process. So if in a group of 3 pollers usage percentages per process were 2, 18 and 66, min would return 2 and max would return 66.\\ Processes report what they are doing in shared memory and the self-monitoring process summarizes that data each second. State changes (busy/idle) are registered upon change - thus a process that becomes busy registers as such and doesn'​t change or update the state until it becomes idle. This ensures that even fully hung processes will be correctly registered as 100% busy.\\ Currently, "​busy"​ means "not sleeping",​ but in the future additional states might be introduced - waiting for locks, performing database queries, etc.\\ On Linux and most other systems, resolution is 1/100 of a second.|||Percentage of time.\\ Float. |The following process types are currently supported:\\ **alert manager** - manager of alerter tasks\\ **alerter** - process for sending notifications //(not supported on proxy)//\\ **configuration syncer** - process for managing in-memory cache of configuration data\\ **data sender** - proxy data sender //(not supported on server)//\\ **discoverer** - process for discovery of devices\\ **escalator** - process for escalation of actions //(not supported on proxy)//\\ **heartbeat sender** - proxy heartbeat sender //(not supported on server)//\\ **history syncer** - history DB writer\\ **housekeeper** - process for removal of old historical data\\ **http poller** - web monitoring poller\\ **icmp pinger** - poller for icmpping checks\\ **ipmi manager** - IPMI poller manager\\ **ipmi poller** - poller for IPMI checks\\ **java poller** - poller for Java checks\\ **poller** - normal poller for passive checks\\ **preprocessing manager** - manager of preprocessing tasks //(not supported on proxy)//\\ **preprocessing worker** - process for data preprocessing ​//(not supported on proxy)//\\ **proxy poller** - poller for passive proxies //(not supported on proxy)//\\ **self-monitoring** - process for collecting internal server statistics\\ **snmp trapper** - trapper for SNMP traps\\ **task manager** - process for remote execution of tasks requested by other components (e.g. close problem, acknowledge problem, check item value now, remote command functionality)\\ **timer** - process for evaluation of time-related trigger functions and maintenances //(not supported on proxy)//\\ **trapper** - trapper for active checks, traps, proxy communication\\ **unreachable poller** - poller for unreachable devices\\ **vmware collector** - VMware data collector responsible for data gathering from VMware services\\ \\ Note: You can also see these process types in a server log file.\\ \\ Valid modes are:\\ **avg** - average value for all processes of a given type (default)\\ **count** - returns number of forks for a given process type, **<​state>​** should not be specified\\ **max** - maximum value\\ **min** - minimum value\\ **<​process number>​** - process number (between 1 and the number of pre-forked instances). For example, if 4 trappers are running, the value is between 1 and 4.\\ \\ Valid states are:\\ **busy** - process is in busy state, for example, processing request (default).\\ **idle** - process is in idle state doing nothing.\\ \\ Examples:\\ => zabbix[process,​poller,​avg,​busy] -> average time of poller processes spent doing something during the last minute\\ => %%zabbix[process,"​icmp pinger",​max,​busy]%% -> maximum time spent doing something by any ICMP pinger process during the last minute\\ => %%zabbix[process,"​history syncer",​2,​busy]%% -> time spent doing something by history syncer number 2 during the last minute\\ => zabbix[process,​trapper,​count] -> amount of currently running trapper processes\\ \\ This item is supported starting with Zabbix **1.8.5.** ​ |
 | |||||| | ||||||
 ^zabbix[proxy,<​name>,<​param>​] ​ |||||| ^zabbix[proxy,<​name>,<​param>​] ​ ||||||