Zabbix Documentation 4.4

2.23.04.04.2 (current)In development:4.4 (devel)Unsupported:1.82.02.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 [2019/02/08 12:33]
martins-v removing default value for StatsAllowedIP
manual:appendix:config:zabbix_proxy [2019/07/05 07:35] (current)
akozlovs
Line 24: Line 24:
 | HistoryCacheSize| no | 128K-2G |16M |Size of history cache, in bytes.\\ Shared memory size for storing history data. | | HistoryCacheSize| no | 128K-2G |16M |Size of history cache, in bytes.\\ Shared memory size for storing history data. |
 | HistoryIndexCacheSize| no | 128K-2G |4M |Size of history index cache, in bytes.\\ Shared memory size for indexing history data stored in history cache.\\ The index cache size needs roughly 100 bytes to cache one item. \\ This parameter is supported since Zabbix 3.0.0. | | HistoryIndexCacheSize| no | 128K-2G |4M |Size of history index cache, in bytes.\\ Shared memory size for indexing history data stored in history cache.\\ The index cache size needs roughly 100 bytes to cache one item. \\ This parameter is supported since Zabbix 3.0.0. |
-| Hostname| no | |Set by HostnameItem |Unique, case sensitive Proxy name. Make sure the proxy name is known to the server!\\ Allowed characters: alphanumeric,​ '​.',​ ' ', '​_'​ and '​-'​.\\ Maximum length: ​64|+| Hostname| no | |Set by HostnameItem |Unique, case sensitive Proxy name. Make sure the proxy name is known to the server!\\ Allowed characters: alphanumeric,​ '​.',​ ' ', '​_'​ and '​-'​.\\ Maximum length: ​128|
 | HostnameItem| no | |system.hostname |Item used for setting Hostname if it is undefined (this will be run on the proxy similarly as on an agent).\\ Does not support UserParameters,​ performance counters or aliases, but does support system.run[].\\ \\ Ignored if Hostname is set.\\ \\ This parameter is supported since Zabbix 1.8.6. | | HostnameItem| no | |system.hostname |Item used for setting Hostname if it is undefined (this will be run on the proxy similarly as on an agent).\\ Does not support UserParameters,​ performance counters or aliases, but does support system.run[].\\ \\ Ignored if Hostname is set.\\ \\ This parameter is supported since Zabbix 1.8.6. |
 | HousekeepingFrequency| no | 0-24 |1 |How often Zabbix will perform housekeeping procedure (in hours).\\ Housekeeping is removing outdated information from the database.\\ //Note//: To prevent housekeeper from being overloaded (for example, when configuration parameters ProxyLocalBuffer or ProxyOfflineBuffer are greatly reduced), no more than 4 times HousekeepingFrequency hours of outdated information are deleted in one housekeeping cycle. Thus, if HousekeepingFrequency is 1, no more than 4 hours of outdated information (starting from the oldest entry) will be deleted per cycle.\\ //Note//: To lower load on proxy startup housekeeping is postponed for 30 minutes after proxy start. Thus, if HousekeepingFrequency is 1, the very first housekeeping procedure after proxy start will run after 30 minutes, and will repeat every hour thereafter. This postponing behavior is in place since Zabbix 2.4.0.\\ Since Zabbix 3.0.0 it is possible to disable automatic housekeeping by setting HousekeepingFrequency to 0. In this case the housekeeping procedure can only be started by //​housekeeper_execute//​ runtime control option and the period of outdated information deleted in one housekeeping cycle is 4 times the period since the last housekeeping cycle, but not less than 4 hours and not greater than 4 days. | | HousekeepingFrequency| no | 0-24 |1 |How often Zabbix will perform housekeeping procedure (in hours).\\ Housekeeping is removing outdated information from the database.\\ //Note//: To prevent housekeeper from being overloaded (for example, when configuration parameters ProxyLocalBuffer or ProxyOfflineBuffer are greatly reduced), no more than 4 times HousekeepingFrequency hours of outdated information are deleted in one housekeeping cycle. Thus, if HousekeepingFrequency is 1, no more than 4 hours of outdated information (starting from the oldest entry) will be deleted per cycle.\\ //Note//: To lower load on proxy startup housekeeping is postponed for 30 minutes after proxy start. Thus, if HousekeepingFrequency is 1, the very first housekeeping procedure after proxy start will run after 30 minutes, and will repeat every hour thereafter. This postponing behavior is in place since Zabbix 2.4.0.\\ Since Zabbix 3.0.0 it is possible to disable automatic housekeeping by setting HousekeepingFrequency to 0. In this case the housekeeping procedure can only be started by //​housekeeper_execute//​ runtime control option and the period of outdated information deleted in one housekeeping cycle is 4 times the period since the last housekeeping cycle, but not less than 4 hours and not greater than 4 days. |
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>​\\ LoadModule=</​abs_path/​module.so>​\\ Either the module ​must be located in directory specified by LoadModulePath ​or 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 65: Line 65:
 | 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.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.2.0. ​ |
 | 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. ​ |