This KB article seems to indicate that there is a bug in Win2008 wherein external monitors polling of Remote Registry causes a memory leak. Once we disabled the monitor (and restarted the service), this issues has gone away. The Remote Registry component monitor was one of the monitors enabled in the Windows 2003-2008 template. The first process identified was for Remote Registry. We have lateley seen several servers with svchost processes consuming 1GB or more memory. I have brought this up to them (along with the fact that all the services that they are monitoring can be monitored in SW) but until they get it figured out, I was hoping that someone could explain to me how I can set this to only send an alert if it fails for 3 consecutive polls.įinally, and I'm not sure that this has anything to do with it, when I do get application down alerts they showing up as a 500 Internal Server Error. This alert only seems to be triggering on one of the servers, which tells me that I set the monitor and alert up correctly, so the problem therefore lies with the alerting server. I then set up an alert based on this http monitor which looks like this:īecause the alert was triggering, literally, every poll, I changed the polling frequency on the application monitor to every 10 minutes, and as you see the condition must exist for more than 20 minutes. The http monitor is set up to go to the URL and then search the URL for a NOT_AVAILABLE ![]() I have set up an HTTP QoE monitor that is checks the webpage to see if any of the services are not available. I have a pair of Linux servers, which have a java based program that monitors six services and then outputs the results of that to a webpage. I'm hoping that one of the resident SW guru's can help me out with setting up an alert that is absolutely giving me fits.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |