"hmmm that's a different type of reporting then the one I was thinking about." You know me Dirk, always throwing the curve balls.....
-Tom -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Sent: Friday, August 29, 2008 10:51 AM To: Servers Alive Discussion List Subject: RE: [SA-list] Servers Alive and reporting hmmm that's a different type of reporting then the one I was thinking about. Some of them can be done. You can create an HTML template that lists all entries ordered by hostname (add the NOGROUP sorting too) and you can also order by checktype. The alerts that are configured can be seen within the HTML template based output too (sa_alerts). What alerts does John Smith get via email is a difficult one....that would mean that a filtering has to be possible to a person that is part of an alert....that is not (yet?) possible. Dirk Bulinckx. -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Vogl, Tom Sent: Friday, August 29, 2008 4:40 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Servers Alive and reporting Dirk, Configuration reporting is a big issue for us: -Are all our alerts set up correctly? -Are checks, timeouts and security settings accurate across servers? -What checks exist for a specific server? -What alerts does John Smith get via email? -What servers have a ping check? -etc.... All of these could be on demand, we don't need them to be scheduled. -Tom -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Sent: Friday, August 29, 2008 5:51 AM To: Servers Alive Discussion List Subject: [SA-list] Servers Alive and reporting 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 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.= 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. 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.
