Nagios Support Forum

Hello Support

When Host Windows Server with NCPA Agent is undergoing 100% CPU usage

Is there a way for NagiosXI to alert us if a windows server is not responding since ping and telnet are working normally in this case?

or Is there a way to that NagiosXI know that no available resources for an NCPA agent to run on a windows server?

Thanks
Insurity

Don't NCPA checks fail when there are "no available resources for an NCPA agent to run on a windows server"? Do you get notifications for the services in hard critical state? What is the status of the "CPU Usage" service?

So what I am getting with 100% CPU on the host

is all NCPA checks returning delayed feed back of - (Service check timed out after 60.01 seconds)

Is there another way to get notified earlier on such use-case? for example another check not through NCPA?

Below is the email that is sent which is not clear that the CPU is 100% and that is why the agent wasnt able to processes monitoring
***** Nagios XI Alert *****
Nagios has detected a problem with this service.
Notification Type: PROBLEM
Service: Srv H Grp - Disk Usage on C:/
Host:
Address:
State: CRITICAL
Info:
(Service check timed out after 61.01 seconds)
Date/Time: 2019-06-20 13:54:5
As for the PING it's status is OK

Thanks
Insurity

Is there another way to get notified earlier on such use-case? for example another check not through NCPA?

Checking internals (various metrics on your server) would always require some type of agent. Even with "agentless" monitoring, e.g. using wmi or snmp, the system would need to have enough resources to perform the checks... NCPA does not require lots of CPU power to run, so I don't think using a different agent would solve the issue.

I would recommend that you find out what is causing the CPU spikes on the Windows server, and fix the issue, so that you could successfully monitor various metrics - disk usage, memory, etc.

Are you using active or passive NCPA checks? Can you post the ncpa_listener.log, ncpa_passive.log, win32service_ncpalistener.log, and win32service_ncpapassive.log on the forum. Please remove/obfuscate sensitive data.

Thanks

I will give a try through WMI call since the agent didnt have resources to run in this use case

Sounds good. We will keep the thread for the time being. Thank you!