Hello,

I’ve run into an issue while using check_nt to monitor CPU load on windows 
servers from my instance of Nagios core. I’m running NSClient 3.8 or 4.3 and it 
has become apparent that the CPU utilization information I receive back is only 
ever for CPU 0 and not the total system load. I’ve been able to replicate this 
issue on multiple systems and I’m wondering if I’m missing a variable  in my 
config. An example of how I’m using the plugin is:

In the cfg for a system:

define service{
        use                     247service
        host_name               HOSTNAME
        service_description     CPU Load
        check_command           check_nt!CPULOAD!-l 5,80,90
        }

And I’ve defined the command in commands.cfg under objects:

define command{
        command_name    check_nt
        command_line    $USER1$/check_nt -H $HOSTADDRESS$ -p 12489 -s PASSWORD 
-v $ARG1$ $ARG2$
        }

I’ve checked multiple forums and I’m not seeing a similar reported issue so I’m 
wondering if I am just missing something obvious.

Thanks,
Andrew


Andrew Mayer | SpiderRock | 300 S. RiverSide Plaza | Suite 2350 | Chicago, IL 
60606
Office: 312.256.9620 | Fax: 312.256.9640 |
E-Mail: [email protected]<mailto:[email protected]>

Client Support: 312.256.9602 | [email protected]<mailto:[email protected]> 
| AIM: spiderrockcs | gChat: spiderrockcs





--
Important - Confidential Information & Disclaimer. All email sent to or from 
this address will be retained by SpiderRock’s email archiving system. This 
message is intended only for the use of the individual or entity to which it is 
addressed, and may contain information that is privileged, confidential, and 
exempt from disclosure under applicable law. Please do not forward or 
distribute this correspondence by any means. Please also be aware that there is 
no assumption of privacy in any SpiderRock communication. If you have received 
this message in error, please notify us immediately and delete the message 
without copying or forwarding it to anyone. SpiderRock will not be liable for 
any compliance and technical information or guidance provided herein.

Reply via email to