Zabbix Documentation 4.2

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

User Tools

Site Tools


manual:appendix:config:zabbix_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:appendix:config:zabbix_proxy [2018/10/01 09:42]
127.0.0.1 external edit
manual:appendix:config:zabbix_proxy [2019/08/29 05:22] (current)
martins-v adding the missing StartPreprocessors parameter
Line 15: Line 15:
 | DBSocket| no | |3306 |Path to MySQL socket.\\ Database port when not using local socket. Ignored for SQLite. | | DBSocket| no | |3306 |Path to MySQL socket.\\ Database port when not using local socket. Ignored for SQLite. |
 | DBUser| | | |Database user. Ignored for SQLite. | | DBUser| | | |Database user. Ignored for SQLite. |
-| DataSenderFrequency| no | 1-3600 |1 |Proxy will send collected data to the server every N seconds.\\ Active proxy parameter. Ignored for passive proxies (see ProxyMode parameter). ​ |+| DataSenderFrequency| no | 1-3600 |1 |Proxy will send collected data to the server every N seconds. Note that active proxy will still poll Zabbix server every second for remote command tasks.\\ Active proxy parameter. Ignored for passive proxies (see ProxyMode parameter). ​ |
 | DebugLevel| no | 0-5 |3 |Specifies debug level:\\ 0 - basic information about starting and stopping of Zabbix processes\\ 1 - critical information\\ 2 - error information\\ 3 - warnings\\ 4 - for debugging (produces lots of information)\\ 5 - extended debugging (produces even more information) | | DebugLevel| no | 0-5 |3 |Specifies debug level:\\ 0 - basic information about starting and stopping of Zabbix processes\\ 1 - critical information\\ 2 - error information\\ 3 - warnings\\ 4 - for debugging (produces lots of information)\\ 5 - extended debugging (produces even more information) |
 | EnableRemoteCommands| no | |0 |Whether remote commands from Zabbix server are allowed.\\ 0 - not allowed\\ 1 - allowed\\ This parameter is supported since Zabbix 3.4.0. | | EnableRemoteCommands| no | |0 |Whether remote commands from Zabbix server are allowed.\\ 0 - not allowed\\ 1 - allowed\\ This parameter is supported since Zabbix 3.4.0. |
Line 32: Line 32:
 | ListenIP| no | |0.0.0.0 |List of comma delimited IP addresses that the trapper should listen on.\\ Trapper will listen on all network interfaces if this parameter is missing.\\ Multiple IP addresses are supported since Zabbix 1.8.3. | | ListenIP| no | |0.0.0.0 |List of comma delimited IP addresses that the trapper should listen on.\\ Trapper will listen on all network interfaces if this parameter is missing.\\ Multiple IP addresses are supported since Zabbix 1.8.3. |
 | ListenPort| no | 1024-32767 |10051 |Listen port for trapper. | | ListenPort| no | 1024-32767 |10051 |Listen port for trapper. |
-| LoadModule| no |  |  |Module to load at proxy startup. Modules are used to extend functionality of the proxy.\\ ​Format: LoadModule=<​module.so>​\\ ​The modules ​must be located in directory specified by LoadModulePath.\\ It is allowed to include multiple LoadModule parameters. ​ |+| LoadModule| no |  |  |Module to load at proxy startup. Modules are used to extend functionality of the proxy.\\ ​Formats:\\ LoadModule=<​module.so>​\\ ​LoadModule=<​path/​module.so>​\\ (since 4.2.3) LoadModule=</​abs_path/​module.so>​\\ Either the module ​must be located in directory specified by LoadModulePath ​or (since 4.2.3) the path must precede the module name. If the preceding path is absolute (starts with '/'​) then LoadModulePath is ignored.\\ It is allowed to include multiple LoadModule parameters. ​ |
 | LoadModulePath| no |  |  |Full path to location of proxy modules.\\ Default depends on compilation options. ​ | | LoadModulePath| no |  |  |Full path to location of proxy modules.\\ Default depends on compilation options. ​ |
 | LogFile| yes, if LogType is set to //file//, otherwise\\ no | | |Name of log file. | | LogFile| yes, if LogType is set to //file//, otherwise\\ no | | |Name of log file. |
Line 60: Line 60:
 | StartPollersUnreachable| no | 0-1000 |1 |Number of pre-forked instances of pollers for unreachable hosts (including IPMI and Java).\\ Since Zabbix 2.4.0, at least one poller for unreachable hosts must be running if regular, IPMI or Java pollers are started.\\ The upper limit used to be 255 before version 1.8.5.\\ This option is missing in version 1.8.3. | | StartPollersUnreachable| no | 0-1000 |1 |Number of pre-forked instances of pollers for unreachable hosts (including IPMI and Java).\\ Since Zabbix 2.4.0, at least one poller for unreachable hosts must be running if regular, IPMI or Java pollers are started.\\ The upper limit used to be 255 before version 1.8.5.\\ This option is missing in version 1.8.3. |
 | StartPollers| no | 0-1000 |5 |Number of pre-forked instances of pollers.\\ The upper limit used to be 255 before version 1.8.5. | | StartPollers| no | 0-1000 |5 |Number of pre-forked instances of pollers.\\ The upper limit used to be 255 before version 1.8.5. |
 +| StartPreprocessors| no | 1-1000 |3 |Number of pre-forked instances of preprocessing workers**<​sup>​[[zabbix_server#​footnotes|1]]</​sup>​**.\\ The preprocessing manager process is automatically started when a preprocessor worker is started.\\ This parameter is supported since Zabbix 4.2.0. ​ |
 | StartSNMPTrapper| no | 0-1 |0 |If set to 1, SNMP trapper process will be started.\\ This parameter is supported since Zabbix 2.0.0. ​ | | StartSNMPTrapper| no | 0-1 |0 |If set to 1, SNMP trapper process will be started.\\ This parameter is supported since Zabbix 2.0.0. ​ |
 | StartTrappers| no | 0-1000 |5 |Number of pre-forked instances of trappers.\\ Trappers accept incoming connections from Zabbix sender and active agents.\\ The upper limit used to be 255 before version 1.8.5. | | StartTrappers| no | 0-1000 |5 |Number of pre-forked instances of trappers.\\ Trappers accept incoming connections from Zabbix sender and active agents.\\ The upper limit used to be 255 before version 1.8.5. |
 | StartVMwareCollectors| no |0-250 ​ |0  |Number of pre-forked vmware collector instances.\\ This parameter is supported since Zabbix 2.2.0. | | StartVMwareCollectors| no |0-250 ​ |0  |Number of pre-forked vmware collector instances.\\ This parameter is supported since Zabbix 2.2.0. |
 +| StatsAllowedIP| no |  |  |List of comma delimited IP addresses, optionally in CIDR notation, or DNS names of external Zabbix instances. Stats request will be accepted only from the addresses listed here. If this parameter is not set no stats requests will be accepted.\\ If IPv6 support is enabled then '​127.0.0.1',​ '::​127.0.0.1',​ '::​ffff:​127.0.0.1'​ are treated equally and '::/​0'​ will allow any IPv4 or IPv6 address. '​0.0.0.0/​0'​ can be used to allow any IPv4 address.\\ Example: StatsAllowedIP=127.0.0.1,​192.168.1.0/​24,::​1,​2001:​db8::/​32,​zabbix.example.com\\ This parameter is supported since Zabbix 4.0.5. ​ |
 | Timeout| no | 1-30 |3 |Specifies how long we wait for agent, SNMP device or external check (in seconds). | | Timeout| no | 1-30 |3 |Specifies how long we wait for agent, SNMP device or external check (in seconds). |
-| TLSAccept| yes, if TLS certificate or PSK parameters are defined (even for //​unencrypted//​ connection),​ otherwise no |  | |What incoming connections to accept from Zabbix server. Used for a passive proxy, ignored on an active proxy. Multiple values can be specified, separated by comma: \\ //​unencrypted//​ - accept connections without encryption (default) \\ //psk// - accept connections with TLS and a pre-shared key (PSK) \\ //cert// - accept connections with TLS and a certificate\\ This parameter is supported since Zabbix 3.0.0. ​ |+| TLSAccept| yes for passive proxy, if TLS certificate or PSK parameters are defined (even for //​unencrypted//​ connection),​ otherwise no |  | |What incoming connections to accept from Zabbix server. Used for a passive proxy, ignored on an active proxy. Multiple values can be specified, separated by comma: \\ //​unencrypted//​ - accept connections without encryption (default) \\ //psk// - accept connections with TLS and a pre-shared key (PSK) \\ //cert// - accept connections with TLS and a certificate\\ This parameter is supported since Zabbix 3.0.0. ​ |
 | TLSCAFile| no |  | |Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification,​ used for encrypted communications between Zabbix components.\\ This parameter is supported since Zabbix 3.0.0. ​ | | TLSCAFile| no |  | |Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification,​ used for encrypted communications between Zabbix components.\\ This parameter is supported since Zabbix 3.0.0. ​ |
 | TLSCertFile| no |  | |Full pathname of a file containing the proxy certificate or certificate chain, used for encrypted communications between Zabbix components.\\ This parameter is supported since Zabbix 3.0.0. ​ | | TLSCertFile| no |  | |Full pathname of a file containing the proxy certificate or certificate chain, used for encrypted communications between Zabbix components.\\ This parameter is supported since Zabbix 3.0.0. ​ |
-| TLSConnect| yes, if TLS certificate or PSK parameters are defined (even for //​unencrypted//​ connection),​ otherwise no |  | |How the proxy should connect to Zabbix server. Used for an active proxy, ignored on a passive proxy. Only one value can be specified: \\ //​unencrypted//​ - connect without encryption (default) \\ //psk// - connect using TLS and a pre-shared key (PSK) \\ //cert// - connect using TLS and a certificate\\ This parameter is supported since Zabbix 3.0.0. ​ |+| TLSConnect| yes for active proxy, if TLS certificate or PSK parameters are defined (even for //​unencrypted//​ connection),​ otherwise no |  | |How the proxy should connect to Zabbix server. Used for an active proxy, ignored on a passive proxy. Only one value can be specified: \\ //​unencrypted//​ - connect without encryption (default) \\ //psk// - connect using TLS and a pre-shared key (PSK) \\ //cert// - connect using TLS and a certificate\\ This parameter is supported since Zabbix 3.0.0. ​ |
 | TLSCRLFile| no |  | |Full pathname of a file containing revoked certificates.This parameter is used for encrypted communications between Zabbix components.\\ This parameter is supported since Zabbix 3.0.0. ​ | | TLSCRLFile| no |  | |Full pathname of a file containing revoked certificates.This parameter is used for encrypted communications between Zabbix components.\\ This parameter is supported since Zabbix 3.0.0. ​ |
 | TLSKeyFile| no |  | |Full pathname of a file containing the proxy private key, used for encrypted communications between Zabbix components.\\ This parameter is supported since Zabbix 3.0.0. ​ | | TLSKeyFile| no |  | |Full pathname of a file containing the proxy private key, used for encrypted communications between Zabbix components.\\ This parameter is supported since Zabbix 3.0.0. ​ |