I agree completely.   The logging is available.   Many other programs (that 
cost much more money) handle their own reporting.    We have developed our own 
reporting mechanisms, however, it might be nice if Servers Alive offered 
reporting.   Perhaps and add on at additional charge.   Pretty charts, graphs, 
and raw data tables would go along way to bringing server's alive into the 
multi-tiered enterprise.    

I have recommended Servers Alive to MANY companies here.   I don't know if they 
took my advice or not, but until I have a service provider call me and tell me 
that my network is down before I call them and they say "hm, sure enough I see 
an alarm", I will not switch my monitoring solution.   

Jason Passow
Mississippi Welders Supply
http://www.mwsco.com
[EMAIL PROTECTED]
ph: (507) 494-5178
fax: (507) 454-8104



--------------------------------------------------------------------------------

From: Dirk [mailto:[EMAIL PROTECTED]
To: Servers Alive Discussion List [mailto:[EMAIL PROTECTED]
Sent: Fri, 29 Aug 2008 10:10:17 -0500
Subject: RE: [SA-list] Servers Alive and reporting



Now that I think about this logging is already done by Servers Alive, you just 
can't use Servers ALive to get a report of it. 

This is exactly what the statistical logging does. 

It tells you when the entry changed from status_A to status_B and how long it 
was in status_B before changing. 

 

 

Dirk Bulinckx. 

From: Servers Alive Discussion List [mailto:salive@woodstone.nu 
(mailto:salive@woodstone.nu)] On Behalf Of Brett Hanson
Sent: Friday, August 29, 2008 4:41 PM
To: Servers Alive Discussion List
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 (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.

Reply via email to