The first thing I would do is go to someplace like Montastic and sign up. Add your URL and it will provide a basic "internet" view of availability.
In Servers Alive turn monitoring up to maximum and let it run for a cycle or two with the failures. The turn the monitoring back to normal. In the log find the error being returned to Servers Alive. This will be the first indication of what is wrong. From your other message it seems to be looking for non-existent content. Once that has been identified corrective actions can be created. If it's timing out but the site is up, increase the timeout. If it's a content issue, correct that or create a "status" page that is static content( simply says OK). Other issues may be occurring but those are the primary ones. -Kevin On Wed, Dec 9, 2009 at 9:50 AM, Griffin, Jim <jgrif...@kepner-tregoe.com (mailto:jgrif...@kepner-tregoe.com)> wrote: We have a web developer who has access to our hosting company/website. So she is able to look and see that yes indeed our website is up, yet SA reports it as down. I have tried changing the timeout on the alert but this has not helped either. I hear what you are saying Kevin but how can I go about finding the condition. >From what I was told, all was fine until about a month ago. Should the >hosting company be contacted to help investigate this as well? Jim -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:salive@woodstone.nu (mailto:salive@woodstone.nu)] On Behalf Of Kevin Stone Sent: Tuesday, December 08, 2009 12:46 PM To: Servers Alive Discussion List Subject: Re: [SA-list] Application - False Positives and how is this being confirmed? Are you at the same site and within the same minute? One issue with monitoring external sites is that you can never fully replicate the exact conditions that occurred at the moment SA reported the failure. Monitoring tools never report false positives, something triggered the condition from the viewpoint of the tool. The trick is finding that condition. What error is being reported, a timeout? -Kevin On Tue, Dec 8, 2009 at 12:10 PM, Griffin, Jim <jgrif...@kepner-tregoe.com (mailto:jgrif...@kepner-tregoe.com)> wrote: Because its reporting our website as being down when in fact its up. -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:salive@woodstone.nu (mailto:salive@woodstone.nu)] On Behalf Of Kevin Stone Sent: Tuesday, December 08, 2009 11:06 AM To: Servers Alive Discussion List Subject: Re: [SA-list] Application - False Positives How do you know it's a false positive? -Kevin On Tue, Dec 8, 2009 at 10:50 AM, Griffin, Jim <jgrif...@kepner-tregoe.com (mailto:jgrif...@kepner-tregoe.com)> wrote: That is my problem as well. Too many false positives. Im running Windows Server 2000 Service Pack 4. Servers Alive version 6.1.2247. This alert is specifically for checking our company website (which is hosted externally). What other information do you need? You may have to walk me though getting what you need as Im not really familiar with the product. Jim -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:salive@woodstone.nu (mailto:salive@woodstone.nu)] On Behalf Of Dirk Bulinckx Sent: Tuesday, December 08, 2009 10:31 AM To: Servers Alive Discussion List Subject: RE: [SA-list] Application - False Positives And what does SA show as reason for the down? And what exact version/build of SA are you using? dirk From: Servers Alive Discussion List [mailto:salive@woodstone.nu (mailto:salive@woodstone.nu)] On Behalf Of Laatz, Anthony Sent: Tuesday, December 08, 2009 3:56 PM To: Servers Alive Discussion List Subject: [SA-list] Application - False Positives Ive noticed more recently that we are starting to get a lot of false positives when SA is checking to see if an application is running. We have SA checking every 2 minutes during the day and every 3 overnight and weekend. It was checking every minute on off hours but we had 12 hours of false positives flood us this past weekend. I have increased the timeout for the application check to 30 seconds, but it doesnt seem to be enough. I also configured SA to not report an application down until two checks in a row fail. Does anyone have any ideas on how to reduce or eliminate the number of false positives? Thank you, Anthony Laatz | Network Administrator Answer Center America, Inc. | Phone: (800) 270-7030 | Private Fax: (866) 827-8802 Visit Our Website (http://www.goacanow.com/) | Visit Our Blog (http://blog.goacanow.com/) | Email Me (mailto:ala...@acanow.com) | Follow Us On Twitter (http://www.twitter.com/goacanow) | Fan Us On Facebook (http://www.facebook.com/pages/Answer-Center-America/106031356597) ________________________________ This e-mail may contain Answer Center America Company proprietary information intended for the sole use of the recipient(s). Any use by others is prohibited. If you are not the intended recipient, please contact the sender and delete all copies of the message. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu (mailto:salive@woodstone.nu) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu (mailto:salive@woodstone.nu) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu (mailto:salive@woodstone.nu) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu (mailto:salive@woodstone.nu) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu (mailto:salive@woodstone.nu) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu (mailto:salive@woodstone.nu) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu (mailto:salive@woodstone.nu) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list.
