WMI Monitoring

I am getting disk space alerts that I should be getting.



Last Error

DISK C Warning level: 67 (returned value) less than 300|95|5|8



the 300 is the ping time

the 95 is the used cpu

the 5 is the available memory

and the 8 is the available disk space



I have other alerts where it is confusing the thresholds of the Windows health monitor. Deleting and re adding the monitor doesnt fix this problem. What can I do to resolve this?

Anything on this because a majority of my windows health monitors are having this problem.

What version and release are you using?

I am running the Premium edition version 9.0.9

This issue is slowly making its way to all of my Windows health monitors.

This issue is occurring for all of the windows health monitors

1) Is it constantly reporting those values?

2) What is the content of your value-errors.log file in the logging subdirectory?

No its random on the errors its reporting, but what it appears is it is mixing the thresholds for different items, such as the ping threshold mixed with the disk space threshold.



I dont have a value-errors.log in the logging subdirectory.

This is happening for more than one device. When the device and monitor is originally setup it runs correctly and alerts correctly, then after a while it starts sending these bogus messages. Deleting and readding the monitor works, but again after sometime it sends the bogus messages again. It almost seems like the configuration for the monitoring rules becomes corrupted or out of order for what it is expecting.



I need to know how to resolve this issue permanently, thank you.

Still having issues with the Windows Health monitors.



It sends alerts when there is no alert and when sending an alert its confusing the message it is supposed to send in the alert.



I have recently upgraded to the latest version, and this issue is still occurring. I really like ServersCheck, i hope we can get this issue resolved.

Is it doing this for all Windows checks?



If so, then best is to run the monitoring_thread2.exe in debug mode:

1) stop the ServersCheck service

2) from the command prompt, start following processes in the main ServersCheck directory:

- s-graphs.exe

- s-alerts.exe

then type

monitoring_thread2.exe > log.txt



As soon as you get again such a false alert, then open up the log.txt and look in that file for the part of the bogus alert message. Copy paste that section as a reply

Here is an exerpt from the log.txt file.



S-14 Sun May 20 20:35:49 2012 save 13372734811977WINDOWSHEALTH<!!>1337567749<!!>5057<!!>0<!!>1337567749<!!>

# S-14 Sun May 20 20:35:49 2012 13372734811977WINDOWSHEALTH - s:OK - e:DISK C Warning level: 88 (returned value) less than 300|95|5|8 - v:58|0|77|C.88 - t:1337567749

# S-14 Sun May 20 20:35:49 2012 13372734811977WINDOWSHEALTH - finished in 4 sec

# S-X Sun May 20 20:35:49 2012 Check down status for 13334693441514SERVICES 22863

Here is another example





# S-2 Sun May 20 20:39:41 2012 save 13373481861051WINDOWSHEALTH<!!>1337567981<!!>4572<!!>0<!!>1337567981<!!>

# S-2 Sun May 20 20:39:42 2012 13373481861051WINDOWSHEALTH - s:OK - e:CPU CPU Error level: 7 (returned value) greater than - v:51|1|53|C.75|E.92 - t:206

# S-2 Sun May 20 20:39:42 2012 13373481861051WINDOWSHEALTH - finished in 13 sec

# S-X Sun May 20 20:39:42 2012 Check down status for 1333469344341SERVICES 25301

Thanks. I have forwarded it to development to look into it. Will revert back to you when I have an update