Return-Path: X-Original-To: apmail-trafficserver-users-archive@www.apache.org Delivered-To: apmail-trafficserver-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B1079188B8 for ; Tue, 30 Jun 2015 21:46:51 +0000 (UTC) Received: (qmail 15507 invoked by uid 500); 30 Jun 2015 21:46:51 -0000 Delivered-To: apmail-trafficserver-users-archive@trafficserver.apache.org Received: (qmail 15451 invoked by uid 500); 30 Jun 2015 21:46:51 -0000 Mailing-List: contact users-help@trafficserver.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@trafficserver.apache.org Delivered-To: mailing list users@trafficserver.apache.org Received: (qmail 15442 invoked by uid 99); 30 Jun 2015 21:46:51 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Jun 2015 21:46:51 +0000 Received: from [17.149.228.188] (unknown [17.149.228.188]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 319851A0251 for ; Tue, 30 Jun 2015 21:46:51 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\)) Subject: Re: ATS 6.0 Logging Question From: Leif Hedstrom In-Reply-To: Date: Tue, 30 Jun 2015 14:46:51 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <46C033BF-950C-4DB4-AB7E-1DE43AA4D504@apache.org> References: To: users@trafficserver.apache.org X-Mailer: Apple Mail (2.2102) > On Jun 30, 2015, at 5:53 AM, Adam W. Dace = wrote: >=20 > First, let me say the new logging regime is looking good. Really = good. I've had quite the fun time defining my own logging format and it = seems to be working quite well. >=20 > The only thing I miss at all about the old logging system was the idea = that errors get logged into a different file. >=20 > Is there any way to do this in the new regime? I'm guessing not but I = wanted to just ask. That should still be the case. Does it not do that? If so, we have a = serious problem. The =E2=80=9Cnew regime=E2=80=9D is not that new, we = simply removed the hardcoded formats (and related records.config = settings), and moved them all to the XML config file. The error log = should not have changed. =E2=80=94 Leif