Hello,
to all wanting to monitor performance counter values on windows machines, here a quick howto that worked for me.
(For testing i used Zabbix Version 1.1A7 on a server running Debian unstable and a Windows 2000 Prof. Client SP4)
1.) On the client run perfmon and add the counter to see if it works nativly, so without zabbix.
2.) On the client, open your zappit_agentd.conf and add perfmon values. Example:
3.) Add the items via the web-interface. Take the proper name for key as defined in the zabbix_agentd.conf.
From the example above, you would use the following keys:
DiskRead5, DiskWrite5, Interrupts5
4.) Hint: When using examples from other sources, take care of the language of the windows os:
Example (both monitors the same values)
German windows:
PerfCounter= DiskRead5, "\Physikalischer Datenträger(_Total)\Bytes gelesen/s",5
PerfCounter= DiskWrite5, "\Physikalischer Datenträger(_Total)\Bytes geschrieben/s",5
PerfCounter= Interrupts5, "\Prozessor(_Total)\Interrupts/s",5
English windows:
PerfCounter= DiskRead5, "\LogicalDisk(_Total)\Disk Read Bytes/sec",5
PerfCounter= DiskWrite5, "\LogicalDisk(_Total)\Disk Write Bytes/sec",5
PerfCounter= Interrupts5, "\Processor(_Total)\Interrupts/sec",5
5.) On the Windows client restart the zabbix_agentd service.
6.) To ensure all is working, have a look at the zabbix_server.log file on the zabbix server, usally in /tmp/.
Here an example of a failure (in this case because the perfmon values had been set wrong):
7.) In case of an error like mentioned in (6.) fix the problem and re-set the item to "monitored" in the item configuration!
Hope that helps someone ;-)
to all wanting to monitor performance counter values on windows machines, here a quick howto that worked for me.
(For testing i used Zabbix Version 1.1A7 on a server running Debian unstable and a Windows 2000 Prof. Client SP4)
1.) On the client run perfmon and add the counter to see if it works nativly, so without zabbix.
2.) On the client, open your zappit_agentd.conf and add perfmon values. Example:
Code:
PerfCounter= DiskRead5, "\LogicalDisk(_Total)\Disk Read Bytes/sec",5 PerfCounter= DiskWrite5, "\LogicalDisk(_Total)\Disk Write Bytes/sec",5 PerfCounter= Interrupts5, "\Processor(_Total)\Interrupts/sec",5
From the example above, you would use the following keys:
DiskRead5, DiskWrite5, Interrupts5
4.) Hint: When using examples from other sources, take care of the language of the windows os:
Example (both monitors the same values)
German windows:
PerfCounter= DiskRead5, "\Physikalischer Datenträger(_Total)\Bytes gelesen/s",5
PerfCounter= DiskWrite5, "\Physikalischer Datenträger(_Total)\Bytes geschrieben/s",5
PerfCounter= Interrupts5, "\Prozessor(_Total)\Interrupts/s",5
English windows:
PerfCounter= DiskRead5, "\LogicalDisk(_Total)\Disk Read Bytes/sec",5
PerfCounter= DiskWrite5, "\LogicalDisk(_Total)\Disk Write Bytes/sec",5
PerfCounter= Interrupts5, "\Processor(_Total)\Interrupts/sec",5
5.) On the Windows client restart the zabbix_agentd service.
6.) To ensure all is working, have a look at the zabbix_server.log file on the zabbix server, usally in /tmp/.
Here an example of a failure (in this case because the perfmon values had been set wrong):
Code:
030759:20050419:133815 Parameter [Interrupts5] is not supported by agent on host [saturn] 030759:20050419:133910 Parameter [DiskRead5] is not supported by agent on host [ saturn] 030759:20050419:133930 Parameter [DiskWrite5] is not supported by agent on host [saturn]
Hope that helps someone ;-)
Comment