From owner-freebsd-isp@FreeBSD.ORG Tue Nov 18 01:43:17 2003 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5677116A4CE for ; Tue, 18 Nov 2003 01:43:17 -0800 (PST) Received: from mail.tcworks.net (mail.tcworks.net [216.61.218.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71E6343FE0 for ; Tue, 18 Nov 2003 01:43:15 -0800 (PST) (envelope-from ccook@tcworks.net) Received: from tcworks.net (stp.tcworks.net [216.61.218.6]) by mail.tcworks.net (8.12.6/8.12.6) with ESMTP id hAI9XwrM079832; Tue, 18 Nov 2003 03:33:58 -0600 (CST) Sender: xcess@mail.tcworks.net Message-ID: <3FB9EA77.FE1F1398@tcworks.net> Date: Tue, 18 Nov 2003 03:46:31 -0600 From: Chris Cook X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: Marty Landman References: <20031117203641.GG98840@sentex.net> <20031117204102.GI61630@complx.LF.net> <6.0.0.22.0.20031117154856.01b4eb58@pop.face2interface.com> <20031117210935.GK98840@sentex.net> <6.0.0.22.0.20031117163136.03573098@pop.face2interface.com> <6.0.0.22.0.20031117175255.030d6420@pop.face2interface.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-RAVMilter-Version: 8.4.1(snapshot 20020920) (mail.tcworks.net) X-Spam-Status: No, hits=0.0 required=7.0 tests=none autolearn=no version=2.60 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on mail.tcworks.net cc: Damian Gerow cc: isp@freebsd.org Subject: Re: Daily/weekly/monthly output aggregation X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Nov 2003 09:43:17 -0000 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@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. >