2015-03-24 150 views
0

我試圖在Log4J2中實現和配置自定義篩選器 - 基於ThresholdFilter,但打算做更多。我已經看到了自定義appender上的主題,它們遵循相同的插件註釋語法,但尚未在自定義裝配器上找到主題。Log4j2自定義篩選器

MyCustomFilter.java(基於ThresholdFilter)

@Plugin(name = "MyCustomFilter", category = Node.CATEGORY, elementType = Filter.ELEMENT_TYPE, printObject = true) 
public class MyCustomFilter extends AbstractFilter { 

    private static final long serialVersionUID = 1L; 

    private final Level level; 

    private MyCustomFilter(final Level level, final Result onMatch, final Result onMismatch) { 
     super(onMatch, onMismatch); 
     this.level = level; 
    } 

    @Override 
    public Result filter(final Logger logger, final Level level, final Marker marker, final String msg, final Object... params) { 
     return filter(level); 
    } 

    @Override 
    public Result filter(final Logger logger, final Level level, final Marker marker, final Object msg, final Throwable t) { 
     return filter(level); 
    } 

    @Override 
    public Result filter(final Logger logger, final Level level, final Marker marker, final Message msg, final Throwable t) { 
     return filter(level); 
    } 

    @Override 
    public Result filter(final LogEvent event) { 
     return filter(event.getLevel()); 
    } 

    private Result filter(final Level level) { 
     return level.isMoreSpecificThan(this.level) ? onMatch : onMismatch; 
    } 

    @Override 
    public String toString() { 
     return level.toString(); 
    } 

    /** 
    * Create a MyCustomFilter. 
    * 
    * @param level 
    *   The log Level. 
    * @param match 
    *   The action to take on a match. 
    * @param mismatch 
    *   The action to take on a mismatch. 
    * @return The created MyCustomFilter. 
    */ 
    @PluginFactory 
    public static MyCustomFilter createFilter(@PluginAttribute("level") final Level level, @PluginAttribute("onMatch") final Result match, 
      @PluginAttribute("onMismatch") final Result mismatch) { 
     final Level actualLevel = level == null ? Level.ERROR : level; 
     final Result onMatch = match == null ? Result.NEUTRAL : match; 
     final Result onMismatch = mismatch == null ? Result.DENY : mismatch; 
     return new MyCustomFilter(actualLevel, onMatch, onMismatch); 
    } 

} 

log4j2.xml

<?xml version="1.0" encoding="UTF-8"?> 
<Configuration> 

    <MyCustomFilter level="fatal" /> 

    <Appenders> 
    <Console name="STDOUT" target="SYSTEM_OUT"> 
     <PatternLayout pattern="%d %-5p [%c{5}.%M():%L] %m%n" /> 
    </Console> 
    </Appenders> 

    <Loggers> 
    <Logger name="com.me.test.logger" level="info" additivity="false"> 
     <AppenderRef ref="STDOUT" /> 
    </Logger> 

    <!-- Root Logger --> 
    <Root level="warn"> 
     <AppenderRef ref="STDOUT" /> 
    </Root> 
    </Loggers> 

</Configuration> 

LoggingRunner.java

public class LoggingRunner { 

    public static void main(String[] args) { 
     Logger logger = LogManager.getLogger("com.me.test.logger"); 

     logger.fatal("Fatal"); 
     logger.error("Error"); 
     logger.debug("Debug"); 
     logger.info("Info"); 

     System.out.println("end it"); 
    } 

} 

配置語法似乎與Apache文檔中的配置語法相匹配,並模仿ThresholdFilter(一個可用的過濾器)。如果按照圖示放置它,作爲上下文級別篩選器,我沒有看到任何錯誤,但未調用或應用篩選器。

如果我將我的自定義過濾器標籤的追加程序(這是可能與外的現成的過濾器裏面,我得到2015-03-24 16:20:11,713 ERROR AppenderRef contains an invalid element or attribute "MyCustomFilter"

基於Apache Log4J2 documentation並在log42j芯源的例子,我認爲這會工作。

我在做什麼錯?

回答

0

你能告訴你的配置的第一線,在<Configuration>元素?

可以指定<Configuration status="trace">使控制檯上出現log4j的內部日誌記錄,這可能有助於解決問題。

也許log4j無法找到您的插件。

當您編譯插件時,會創建一個序列化的插件列表文件。該文件包含二進制格式的插件名稱和類名。如果這個文件包含在包含你的插件類的jar中,log4j可以找到你的插件。另一種方式來幫助log4j的找到你的插件指定packages屬性您的配置文件:

<Configuration status="trace" packages="com.me.mycustomfilterpackage"> ...

有關更多詳細信息,請參閱this manual page在插件管理如何嘗試查找插件。

+0

關閉未來讀者的循環。似乎添加packages屬性確實有助於PluginManager找到我的過濾器。 – WiSparky82 2015-03-25 14:04:33