Thanks for a great product. I am managing Linux and Windows systems with Check_MK, Nagios and PNP4Nagios. I have an issue which I can’t seem to find an answer for.
I have some Windows perfmon counters I would like to monitor/run checks for. So I followed your directions here: http://mathias-kettner.de/checkmk_windows.html
I run the lodctr command to get the list of counters.
I find the counter reference ID and put this in check_mk.ini. Snippet of my check_mk.ini file:
# Restrict access to certain IP addresses
# only_from = 127.0.0.1 192.168.56.0/24
# Select counters to extract. The following counters
# are needed by checks shipped with check_mk.
# counters = 10332:msx_queues
counters = 13150:MainQueueSize
counters = 13151:MainQueueSize_Num
counters = 13160:PlayerCount
counters = 13161:PlayerCount_Num
counters = 13162:MaxPlayerCount
counters = 13163:MaxPlayerCount_Num
counters = 13414:proc_freq
counters = 13415:proc_freq_mhz
I run from my Nagios box a check_mk –d hostname.fqdn to see what check_mk returns before I start inventorying the system, but I get some miscellaneous data about the perfmon counter and it does not provide me with any appropriate data. Below is a snippet of the data.
Am I doing this correctly and if not, how am I supposed to get appropriate data out of perfmon counters? I can get this data from NSClient++ with some crude Perl scripts on the Nagios end, but it takes a long time for this data to be polled. In the NSClient++ side, I know that if I write some vbscript on the client side and poll the host this way, the check will function much faster, but I rather use Check_MK. In the meantime, since I can’t get check_mk to do this, I will use NSClient++ until that time.
Please let me know if there is anything else I can provide to make the resolution to my problem a lot faster.
Thanks again for a great product.