Daily/weekly/monthly output aggregation

[Chris Cook]

Not that this probably matters too much but I wanted to let you all know
I am in the same exact boat... that is wanting to have perodic output in
a quick, easy to read summary with details available of course.  It is
painful having to read the root emails sometimes :)


-- 
Chris

o----< ccook at tcworks.net >------------------------------------o
|Chris Cook - Admin     |TCWORKS.NET - http://www.tcworks.net |
|The Computer Works ISP |FreeBSD - http://www.freebsd.org     |
o-------------------------------------------------------------o



Marty Landman wrote:
> 
> At 04:49 PM 11/17/2003, Damian Gerow wrote:
> 
> >There's a difference between the system output, and your own script outputs.
> 
> :) -- newbie that I am I understand totally
> 
> >I can read my own script outputs just fine, and generally write the scripts
> >to produce as little output as possible, but I don't want to have to patch
> >every single system we've got to re-write how the system periodic scripts
> >are run.
> 
> Damian I now see your point about stuffing this into a DB; if you can
> categorize it into an enum or even set and normalized particularly here
> where it may be bound to grow and grow (and grow) seems like it could then
> be harvested into a quick daily admin summary email via cron to tell you
> stuff like
> 
> # exceptions in past 24 hrs
> chart of exceptions sources
> breakdown by criticality assignment e.g. inetd > apache > ftpd
> 
> You could even have detailed report links embedded in the email or at least
> on the admin control panel. Hmm, this is starting to sound a like product.
>