manual:appendix:config:zabbix_agentd_win

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
manual:appendix:config:zabbix_agentd_win [2020/02/07 10:46]
martins-v better page structure
manual:appendix:config:zabbix_agentd_win [2020/06/10 18:06]
162.158.255.226 ↷ Links adapted because of a move operation
Line 13: Line 13:
 ^Parameter^Mandatory^Range^Default^Description^ ^Parameter^Mandatory^Range^Default^Description^
 | Alias| no | | |Sets an alias for an item key. It can be used to substitute long and complex item key with a smaller and simpler one.\\ Multiple //Alias// parameters may be present. Multiple parameters with the same //Alias// key are allowed.\\ Different //Alias// keys may reference the same item key.\\ Aliases can be used in //​HostMetadataItem//​ but not in //​HostnameItem//​ or //​PerfCounter//​ parameters.\\ \\ Examples:\\ \\ 1. Retrieving paging file usage in percents from the server.\\ %%Alias=pg_usage:​perf_counter[\Paging File(_Total)\% Usage]%%\\ Now shorthand key **pg_usage** may be used to retrieve data.\\ ​ \\ 2. Getting CPU load with default and custom parameters.\\ Alias=cpu.load:​system.cpu.load\\ Alias=cpu.load[*]:​system.cpu.load[*]\\ This allows use **cpu.load** key to get CPU utilization percentage with default parameters as well as use **cpu.load[percpu,​avg15]** to get specific data about CPU load.\\ \\ 3. Running multiple [[manual/​discovery/​low_level_discovery|low-level discovery]] rules processing the same discovery items.\\ Alias=vfs.fs.discovery[*]:​vfs.fs.discovery\\ Now it is possible to set up several discovery rules using **vfs.fs.discovery** with different parameters for each rule, e.g., **vfs.fs.discovery[foo]**,​ **vfs.fs.discovery[bar]**,​ etc. | | Alias| no | | |Sets an alias for an item key. It can be used to substitute long and complex item key with a smaller and simpler one.\\ Multiple //Alias// parameters may be present. Multiple parameters with the same //Alias// key are allowed.\\ Different //Alias// keys may reference the same item key.\\ Aliases can be used in //​HostMetadataItem//​ but not in //​HostnameItem//​ or //​PerfCounter//​ parameters.\\ \\ Examples:\\ \\ 1. Retrieving paging file usage in percents from the server.\\ %%Alias=pg_usage:​perf_counter[\Paging File(_Total)\% Usage]%%\\ Now shorthand key **pg_usage** may be used to retrieve data.\\ ​ \\ 2. Getting CPU load with default and custom parameters.\\ Alias=cpu.load:​system.cpu.load\\ Alias=cpu.load[*]:​system.cpu.load[*]\\ This allows use **cpu.load** key to get CPU utilization percentage with default parameters as well as use **cpu.load[percpu,​avg15]** to get specific data about CPU load.\\ \\ 3. Running multiple [[manual/​discovery/​low_level_discovery|low-level discovery]] rules processing the same discovery items.\\ Alias=vfs.fs.discovery[*]:​vfs.fs.discovery\\ Now it is possible to set up several discovery rules using **vfs.fs.discovery** with different parameters for each rule, e.g., **vfs.fs.discovery[foo]**,​ **vfs.fs.discovery[bar]**,​ etc. |
-| AllowKey| no | | |Allow execution of those item keys that match a pattern. Key pattern is a wildcard expression that supports "​*"​ character to match any number of any characters.\\ Multiple key matching rules may be defined in combination with DenyKey. The parameters are processed one by one according to their appearance order. If no AllowKey or DenyKey rules defined, all keys are allowed.\\ This parameter is supported since Zabbix 5.0.0.\\ See also: [[:manual/appendix/config/restrict_checks|Restricting agent checks]]. ​ |+| AllowKey| no | | |Allow execution of those item keys that match a pattern. Key pattern is a wildcard expression that supports "​*"​ character to match any number of any characters.\\ Multiple key matching rules may be defined in combination with DenyKey. The parameters are processed one by one according to their appearance order. If no AllowKey or DenyKey rules defined, all keys are allowed.\\ This parameter is supported since Zabbix 5.0.0.\\ See also: [[manual:config:items:restrict_checks|Restricting agent checks]]. ​ |
 | BufferSend| no | 1-3600 |5 |Do not keep data longer than N seconds in buffer. | | BufferSend| no | 1-3600 |5 |Do not keep data longer than N seconds in buffer. |
 | BufferSize| no | 2-65535 |100 |Maximum number of values in a memory buffer. The agent will send\\ all collected data to Zabbix server or proxy if the buffer is full. | | BufferSize| no | 2-65535 |100 |Maximum number of values in a memory buffer. The agent will send\\ all collected data to Zabbix server or proxy if the buffer is full. |
 | 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) |
-| DenyKey| no | | |Deny execution of those item keys that match a pattern. Key pattern is a wildcard expression that supports "​*"​ character to match any number of any characters.\\ Multiple key matching rules may be defined in combination with AllowKey. The parameters are processed one by one according to their appearance order. If no AllowKey or DenyKey rules defined, all keys are allowed.\\ This parameter is supported since Zabbix 5.0.0.\\ See also: [[:manual/appendix/config/restrict_checks|Restricting agent checks]]. ​ |+| DenyKey| no | | |Deny execution of those item keys that match a pattern. Key pattern is a wildcard expression that supports "​*"​ character to match any number of any characters.\\ Multiple key matching rules may be defined in combination with AllowKey. The parameters are processed one by one according to their appearance order. If no AllowKey or DenyKey rules defined, all keys are allowed.\\ This parameter is supported since Zabbix 5.0.0.\\ See also: [[manual:config:items:restrict_checks|Restricting agent checks]]. ​ |
 | EnableRemoteCommands| no | |0 |Whether remote commands from Zabbix server are allowed.\\ 0 - not allowed\\ 1 - allowed\\ This parameter is deprecated, use AllowKey=system.run[*] or DenyKey=system.run[*] instead. | | EnableRemoteCommands| no | |0 |Whether remote commands from Zabbix server are allowed.\\ 0 - not allowed\\ 1 - allowed\\ This parameter is deprecated, use AllowKey=system.run[*] or DenyKey=system.run[*] instead. |
 | HostInterface| no | 0-255 characters | |Optional parameter that defines host interface.\\ Host interface is used at host autoregistration process.\\ An agent will issue an error and not start if the value is over the limit of 255 characters.\\ If not defined, value will be acquired from HostInterfaceItem.\\ Supported since Zabbix 4.4.0. ​ | | HostInterface| no | 0-255 characters | |Optional parameter that defines host interface.\\ Host interface is used at host autoregistration process.\\ An agent will issue an error and not start if the value is over the limit of 255 characters.\\ If not defined, value will be acquired from HostInterfaceItem.\\ Supported since Zabbix 4.4.0. ​ |