Zabbix Documentation 4.2

3.04.04.4 (current)| In development:5.0 (devel)| Unsupported:1.82.02.22.43.23.44.2Guidelines

User Tools

Site Tools


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
manual:appendix:config:zabbix_agentd_win [2019/10/02 08:58]
martins-v numeric path is supported in PerfCounterEn
manual:appendix:config:zabbix_agentd_win [2019/10/02 12:08] (current)
martins-v finding en strings in PerfCounterEn
Line 24: Line 24:
 | MaxLinesPerSecond| no | 1-1000 |20 |Maximum number of new lines the agent will send per second to Zabbix server\\ or proxy processing '​log',​ '​logrt'​ and '​eventlog'​ active checks.\\ The provided value will be overridden by the parameter '​maxlines',​\\ provided in '​log',​ '​logrt'​ or '​eventlog'​ item keys.\\ //Note//: Zabbix will process 10 times more new lines than set in //​MaxLinesPerSecond//​ to seek the required string in log items. | | MaxLinesPerSecond| no | 1-1000 |20 |Maximum number of new lines the agent will send per second to Zabbix server\\ or proxy processing '​log',​ '​logrt'​ and '​eventlog'​ active checks.\\ The provided value will be overridden by the parameter '​maxlines',​\\ provided in '​log',​ '​logrt'​ or '​eventlog'​ item keys.\\ //Note//: Zabbix will process 10 times more new lines than set in //​MaxLinesPerSecond//​ to seek the required string in log items. |
 | PerfCounter| no | | |Syntax: <​parameter_name>,"<​perf_counter_path>",<​period>​\\ Defines new parameter <​parameter_name>​ which is an average value for system performance counter <​perf_counter_path>​ for the specified time period <​period>​ (in seconds).\\ For example, if you wish to receive average number of processor interrupts per second for last minute, you can define new parameter "​interrupts"​ as following:​\\ PerfCounter = interrupts,"​\Processor(0)\Interrupts/​sec",​60\\ Please note double quotes around performance counter path.\\ The parameter name (interrupts) is to be used as the item key when creating an item.\\ Samples for calculating average value will be taken every second.\\ You may run "​typeperf -qx" to get list of all performance counters available in Windows. | | PerfCounter| no | | |Syntax: <​parameter_name>,"<​perf_counter_path>",<​period>​\\ Defines new parameter <​parameter_name>​ which is an average value for system performance counter <​perf_counter_path>​ for the specified time period <​period>​ (in seconds).\\ For example, if you wish to receive average number of processor interrupts per second for last minute, you can define new parameter "​interrupts"​ as following:​\\ PerfCounter = interrupts,"​\Processor(0)\Interrupts/​sec",​60\\ Please note double quotes around performance counter path.\\ The parameter name (interrupts) is to be used as the item key when creating an item.\\ Samples for calculating average value will be taken every second.\\ You may run "​typeperf -qx" to get list of all performance counters available in Windows. |
-| PerfCounterEn| no | | |Syntax: <​parameter_name>,"<​perf_counter_path>",<​period>​\\ Defines new parameter <​parameter_name>​ which is an average value for system performance counter <​perf_counter_path>​ for the specified time period <​period>​ (in seconds).\\ Compared to PerfCounter,​ perfcounter paths must be in English.\\ Supported only on **Windows Server 2008/​Vista** and above.\\ For example, if you wish to receive average number of processor interrupts per second for last minute, you can define new parameter "​interrupts"​ as following:​\\ PerfCounterEn = interrupts,"​\Processor(0)\Interrupts/​sec",​60\\ Please note double quotes around performance counter path.\\ The parameter name (interrupts) is to be used as the item key when creating an item.\\ Samples for calculating average value will be taken every second.\\ You may run "​typeperf -qx" to get list of all performance counters available in Windows.\\ This parameter is supported since Zabbix 4.2.7. ​ |+| PerfCounterEn| no | | |Syntax: <​parameter_name>,"<​perf_counter_path>",<​period>​\\ Defines new parameter <​parameter_name>​ which is an average value for system performance counter <​perf_counter_path>​ for the specified time period <​period>​ (in seconds).\\ Compared to PerfCounter,​ perfcounter paths must be in English.\\ Supported only on **Windows Server 2008/​Vista** and above.\\ For example, if you wish to receive average number of processor interrupts per second for last minute, you can define new parameter "​interrupts"​ as following:​\\ PerfCounterEn = interrupts,"​\Processor(0)\Interrupts/​sec",​60\\ Please note double quotes around performance counter path.\\ The parameter name (interrupts) is to be used as the item key when creating an item.\\ Samples for calculating average value will be taken every second.\\ You can find the list of English strings by viewing the following registry key: ''​HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows ​NT\CurrentVersion\Perflib\009''​.\\ This parameter is supported since Zabbix 4.2.7. ​ |
 | RefreshActiveChecks| no | 60-3600 |120 |How often list of active checks is refreshed, in seconds.\\ Note that after failing to refresh active checks the next refresh will be attempted after 60 seconds. | | RefreshActiveChecks| no | 60-3600 |120 |How often list of active checks is refreshed, in seconds.\\ Note that after failing to refresh active checks the next refresh will be attempted after 60 seconds. |
 | Server| yes, if StartAgents is not explicitly set to 0 | | |List of comma delimited IP addresses, optionally in CIDR notation, or hostnames of Zabbix servers.\\ Incoming connections will be accepted only from the hosts listed here.\\ 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.\\ Note, that "​IPv4-compatible IPv6 addresses"​ (0000::/96 prefix) are supported but deprecated by [[https://​tools.ietf.org/​html/​rfc4291#​section-2.5.5|RFC4291]].\\ Example: Server=127.0.0.1,​192.168.1.0/​24,::​1,​2001:​db8::/​32,​zabbix.domain\\ Spaces are allowed. | | Server| yes, if StartAgents is not explicitly set to 0 | | |List of comma delimited IP addresses, optionally in CIDR notation, or hostnames of Zabbix servers.\\ Incoming connections will be accepted only from the hosts listed here.\\ 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.\\ Note, that "​IPv4-compatible IPv6 addresses"​ (0000::/96 prefix) are supported but deprecated by [[https://​tools.ietf.org/​html/​rfc4291#​section-2.5.5|RFC4291]].\\ Example: Server=127.0.0.1,​192.168.1.0/​24,::​1,​2001:​db8::/​32,​zabbix.domain\\ Spaces are allowed. |