Return-Path: Delivered-To: apmail-logging-log4j-user-archive@www.apache.org Received: (qmail 12986 invoked from network); 30 Nov 2006 09:41:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Nov 2006 09:41:13 -0000 Received: (qmail 92860 invoked by uid 500); 30 Nov 2006 09:41:22 -0000 Delivered-To: apmail-logging-log4j-user-archive@logging.apache.org Received: (qmail 92171 invoked by uid 500); 30 Nov 2006 09:41:20 -0000 Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Users List" Reply-To: "Log4J Users List" Delivered-To: mailing list log4j-user@logging.apache.org Received: (qmail 92160 invoked by uid 99); 30 Nov 2006 09:41:20 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Nov 2006 01:41:20 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [195.112.81.7] (HELO mail.ergonomics.ch) (195.112.81.7) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Nov 2006 01:41:08 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: Re: Log4J System alerts Date: Thu, 30 Nov 2006 10:40:48 +0100 Message-ID: <3FE38194C8A3334A959B64B7D9A1E27B6E31A5@plejaden.seychelles.ergo> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [SPAM (Bayesain Analysis)] - Re: Log4J System alerts - Bayesian Filter detected spam thread-index: AccUB0u8pywErkD2QPuSqFbo3MbDKQAWrAJQ From: "Bender Heri" To: "Log4J Users List" X-Virus-Checked: Checked by ClamAV on apache.org Here a example how to configure filters. Note: Filters are only = available if you use xml configuration. This appender has three filters attached. The first is a log4j built in = filter (LevelRangeFilter), the thow others are self written filters, = derived from org.apache.log4j.spi.Filter which filter LogEvents based on = some values in MDC. If a LogEvent reaches an appender, it is presented to the attached = filters in the order they are configured. The Filter results in: - ACCEPT the LogEvent is accepted, no more further Filters are asked - DENY the Log Event is rejected, no more further Filters are asked - NEUTRAL next filter in chain is asked within a self written Filter you can implement any logic you want. Heri > -----Original Message----- > From: garima015 [mailto:garima_indiya@rediffmail.com] > Sent: Wednesday, November 29, 2006 11:39 PM > To: log4j-user@logging.apache.org >=20 >=20 >=20 > Can you please give me some more idea on how to create that=20 > filter..and how > this will be called >=20 --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org For additional commands, e-mail: log4j-user-help@logging.apache.org