Zabbix Documentation 4.0

3.04.04.2 (current)In development:4.4 (devel)Unsupported:1.82.02.22.43.23.4

User Tools

Site Tools


manual:concepts:proxy

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
manual:concepts:proxy [2018/02/01 06:10]
martins-v utf-8 locale required for proxy
manual:concepts:proxy [2018/11/08 13:46] (current)
martins-v proxy process types can be observed in the proxy log file
Line 15: Line 15:
 See also: [[manual:​distributed_monitoring:​proxies|Using proxies in a distributed environment]] See also: [[manual:​distributed_monitoring:​proxies|Using proxies in a distributed environment]]
  
-=== Proxy process ​===+=== Running proxy ===
  
 == If installed as package == == If installed as package ==
Line 63: Line 63:
 |config_cache_reload|Reload configuration cache. Ignored if cache is being currently loaded.\\ Active Zabbix proxy will connect to the Zabbix server and request configuration data.| | |config_cache_reload|Reload configuration cache. Ignored if cache is being currently loaded.\\ Active Zabbix proxy will connect to the Zabbix server and request configuration data.| |
 |housekeeper_execute|Start the housekeeping procedure. Ignored if the housekeeping procedure is currently in progress.| | |housekeeper_execute|Start the housekeeping procedure. Ignored if the housekeeping procedure is currently in progress.| |
-|log_level_increase[=<​**target**>​]|Increase log level, affects all processes if target is not specified.|**pid** - Process identifier (1 to 65535) \\ **process type** - All processes of specified type (e.g., poller) \\ **process type,N** - Process type and number (e.g., poller,3)|+|log_level_increase[=<​**target**>​]|Increase log level, affects all processes if target is not specified.|**process type** - All processes of specified type (e.g., poller)\\ See all [[#​proxy_process_types|proxy process types]].\\ **process type,N** - Process type and number (e.g., poller,3)\\ **pid** - Process identifier (1 to 65535). For larger values specify target as '​process type,​N'​.  ​|
 |log_level_decrease[=<​**target**>​]|Decrease log level, affects all processes if target is not specified.|:::​| |log_level_decrease[=<​**target**>​]|Decrease log level, affects all processes if target is not specified.|:::​|
- 
-Allowed range of PIDs for changing the log level of a single Zabbx process is from 1 to 65535. On systems with large PIDs <process type,N> target option can be used for changing the log level of a single process. ​ 
  
 Example of using runtime control to reload the proxy configuration cache: Example of using runtime control to reload the proxy configuration cache:
Line 98: Line 96:
  
 See the [[manual:​appendix:​config:​zabbix_proxy|configuration file]] options for details on configuring zabbix_proxy. See the [[manual:​appendix:​config:​zabbix_proxy|configuration file]] options for details on configuring zabbix_proxy.
 +
 +=== Proxy process types ===
 +
 +  * ''​configuration syncer''​ - process for managing in-memory cache of configuration data
 +  * ''​data sender''​ - proxy data sender
 +  * ''​discoverer''​ - process for discovery of devices
 +  * ''​heartbeat sender''​ - proxy heartbeat sender ​
 +  * ''​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
 +  * ''​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)
 +  * ''​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
 +
 +The proxy log file can be used to observe these process types.
 +
 +Various types of Zabbix proxy processes can be monitored using the **zabbix[process,<​type>,<​mode>,<​state>​]** internal [[:​manual/​config/​items/​itemtypes/​internal|item]].
  
 === Supported platforms === === Supported platforms ===