From: Kevin G. <ke...@go...> - 2002-09-09 19:21:40
|
Sorry, Hugh, we haven't implemented anything comparable to LevelMatchFilter yet. Actually, I don't think we've done anything with Filters at all yet. Keep checking back, though, or feel free to suggest an implementation yourself. Hugo Salgado wrote: > Hi, i'd like to use this feature of log4j, but in > the perl version. How can i do it ?? > ----- From log4j FAQ > Is it possible to direct log output to different appenders by level? > Yes it is. Setting the Threshold option of any appender extending > AppenderSkeleton, (most log4j appenders extend AppenderSkeleton) to > filter out all log events with lower level than the value of the > threshold option. > For example, setting the threshold of an appender to DEBUG also allow > INFO, WARN, ERROR and FATAL messages to log along with DEBUG messages. > This is usually acceptable as there is little use for DEBUG messages > without the surrounding INFO, WARN, ERROR and FATAL messages. Similarly, > setting the threshold of an appender to ERROR will filter out DEBUG, > INFO and WARN messages but not ERROR or FATAL messages. > This policy usually best encapsulates what the user actually wants to > do, as opposed to her mind-projected solution. > See examples/sort4.lcf for an example threshold configuration. > If you must filter events by exact level match, then you can attach a > LevelMatchFilter to any appender to filter out logging events by exact > level match. > ------- > Thanks, > Hugo > > ------------------------------------------------------- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > _______________________________________________ > log4perl-devel mailing list > log...@li... > https://lists.sourceforge.net/lists/listinfo/log4perl-devel -- Happy Trails . . . Kevin M. Goess (and Anne and Frank) 904 Carmel Ave. Albany, CA 94706 (510) 525-5217 |