Users should extend this class to implement customized logging event
filtering. Note that
the parent class of all standard appenders, have built-in filtering rules. It is
suggested that you first use and understand the built-in rules before rushing to
write your own custom filters.
This abstract class assumes and also imposes that filters be organized in a linear chain. The #decide decide(LoggerLoggingEvent) method of each filter is called sequentially, in the order of their addition to the chain.
LoggerFilter::decide() method must return one of the integer constants LOG4PHP_LOG4PHP_LOGGER_FILTER_DENY, LOG4PHP_LOGGER_FILTER_NEUTRAL or
If the value LOG4PHP_LOGGER_FILTER_DENY is returned, then the log event is dropped immediately without consulting with the remaining filters.
If the value LOG4PHP_LOGGER_FILTER_NEUTRAL is returned, then the next filter in the chain is consulted. If there are no more filters in the chain, then the log event is logged. Thus, in the presence of no filters, the default behaviour is to log all logging events.
If the value LOG4PHP_LOGGER_FILTER_ACCEPT is returned, then the log event is logged without consulting the remaining filters.
The philosophy of log4php filters is largely inspired from the Linux ipchains.
Direct known subclassesLoggerDenyAllFilter, LoggerLevelMatchFilter, LoggerLevelRangeFilter, LoggerStringMatchFilter
Author: VxR <firstname.lastname@example.org>
Version: $Revision: 1.4 $
Located at libraries/log4php.debug/spi/LoggerFilter.php
Decide what to do.
If the decision is LOG4PHP_LOGGER_FILTER_DENY, then the event will be dropped. If the decision is LOG4PHP_LOGGER_FILTER_NEUTRAL, then the next filter, if any, will be invoked. If the decision is LOG4PHP_LOGGER_FILTER_ACCEPT then the event will be logged without consulting with other filters in the chain.