FYI we write all entries up/down/maintenance to a database. The we query the database for a status change. Therefore if the entry was down when servers alive quit and up when it came back our report would show the down time (inaccurately of course) as reported by servers alive between the down and next up entry.
We archive the data on a time schedule (weekly I think). Then we enter only status change entries (up after down, up after maintenance, etc) and all down cycles. This allows accountability as to why it was down and how long. We would of course see that it was down at 2 am one day (servers alive was shut down at 2:01am) and back up at 7am that morning with no down entries in between we would know that for some reason SA was down but not necessarily the check. This is mostly hypothetical since SA runs as a service that is monitored by another SA instance. SA is not usually down for very long at all except during server reboots where it misses 15 minutes or so. Jason Passow Mississippi Welders Supply http://www.mwsco.com [EMAIL PROTECTED] ph: (507) 494-5178 fax: (507) 454-8104 -------------------------------------------------------------------------------- From: Brett Hanson [mailto:[EMAIL PROTECTED] To: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] Sent: Fri, 29 Aug 2008 09:40:55 -0500 Subject: Re: [SA-list] Servers Alive and reporting One report we've been struggling with for the last couple years is an activity report. We'd like to see a report that shows outages detected by Servers Alive in the past 7 days. This report would show the check name, when the check went down, when it came back up and the duration. Any checks down when the report is run would show as 'Currently Down'. For example: Check Name Down At Up At Outage Duration LDAP Server 27-Aug 4:06 PM 27-Aug 4:32 PM 26 Minutes Service A 29-Aug 3:10 AM Currently Down 5 Hours 17 Minutes Our biggest issue is problems with accuracy that result when Servers Alive is restarted - a check that was down before Servers Alive was shut down and was up when Servers Alive started again is not detected as a status change, and no database record showing the transition exists. Regards, Brett Hanson Systems Analyst Agrium >>> "Dirk" <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> 8/29/2008 3:50 AM >>> One of the often returning question on Servers Alive is if it can do reporting. We always point to the HTML template based output and to the DB logging (using a 3rd party report writer). Still it seems that this is not what people are looking for. That's why we would like you to help us with some brainstorming around that reporting feature. I'll start by giving my own idea on it. * it's based on the HTML template based output * it can be set to be executed (generated) once a day and you can select what "entries" go on it * you can ofcourse have several output's and for several sets of entries * additional parameters are needed like % up cycles % down cycles % maintenance cycles and this per DAY, WEEK, MONTH, YEAR with "easy" access to the current (day/week/...) and the previous (day/week/...) and also access to other days/weeks/months/year. Example: <sa_stats_up_week{pervious}%>gives the up% of the previous week <sa_stats_up_week082008%>gives the up% of week 8 of 2008 <sa_stats_down_month082008%>gives the up% of month 8 of 2008 All ideas/comments/additions are MORE THEN WELCOME Dirk Bulinckx. 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. _____________________________________________________________ IMPORTANT NOTICE ! This E-Mail transmission and any accompanying attachments may contain confidential information intended only for the use of the individual or entity named above. Any dissemination, distribution, copying or action taken in reliance on the contents of this E-Mail by anyone other than the intended recipient is strictly prohibited and is not intended to, in anyway, waive privilege or confidentiality. If you have received this E-Mail in error please immediately delete it and notify sender at the above E-Mail address. Agrium uses state of the art anti-virus technology on all incoming and outgoing E-Mail. We encourage and promote the use of safe E-Mail management practices and recommend you check this, and all other E-Mail and attachments you receive for the presence of viruses. The sender and Agrium accept no liability for any damage caused by a virus or otherwise by the transmittal of this E-Mail. _____________________________________________________________ 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.
