From owner-freebsd-isp Mon Sep 13 3:23:57 1999 Delivered-To: freebsd-isp@freebsd.org Received: from mail.SKINNYHIPPO.COM (mail.SKINNYHIPPO.COM [216.25.13.94]) by hub.freebsd.org (Postfix) with ESMTP id 95BE515047 for ; Mon, 13 Sep 1999 03:23:49 -0700 (PDT) (envelope-from panda@skinnyhippo.com) Received: from egg [202.96.51.68] by mail.SKINNYHIPPO.COM (SMTPD32-5.05) id A0CABF50208; Mon, 13 Sep 1999 06:24:10 -0400 Message-Id: <3.0.5.32.19990913185752.00ad3290@mail.skinnyhippo.com> X-Sender: panda@mail.skinnyhippo.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 13 Sep 1999 18:57:52 +0800 To: freebsd-isp@freebsd.org From: chas Subject: managing huge log files. Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org One of the websites I manage went ballistic 2 weeks ago and has been producing 500+ MB of Apache logs each day. May I ask how people are managing their log files on high-traffic sites ? Performance is key to me so I'm wary of running log analysis software (such as analog) on the server if there's even the possibility of it degrading performance. For the same reason I haven't been doing real-time analysis though I'm not sure if that's valid or not. I've been rotating the logs daily, gzipping and moving off the server but marketing bods want to have log analyses done over the entire month (which is fair enough) as opposed to daily reports. This could work out at 16 GB log files/month once the daily reports are all concat'ed. cheers, chas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message