2

我正在使用 pax-logging-api 和 pax-logging-log4j2 从我的 OSGi 包中进行日志记录。我想利用 Log4J2 的 StructuredDataMessage(使用 EventLogger)将一些消息写入数据库。但是,在使用 Pax 日志记录时,我无法从附加程序中读取放入 StructuredDataMessage 的值。

以下在直接使用 Log4J2 库的非 OSGi 项目中工作

log4j2.properties:

appender.console.type = Console
appender.console.name = STDOUT
appender.console.layout.type = PatternLayout
appender.console.layout.pattern = %m%n

appender.event.type = Console
appender.event.name = event
appender.event.layout.type = PatternLayout
appender.event.layout.pattern = %marker ${sd:id} ${sd:testKey} %n    %m%n

rootLogger.level = debug
rootLogger.appenderRef.console.ref = STDOUT

logger.event.name = EventLogger
logger.event.level = debug
logger.event.appenderRef.console.ref = event
logger.event.additivity = false

测试.java:

public class Test {

    private static final Logger LOGGER = LogManager.getLogger(Test.class);

    public static void main(String[] args) {
        StructuredDataMessage msg = new StructuredDataMessage("1", "message", "event");
        msg.put("testKey", "testValue");

        LOGGER.info(msg);
        EventLogger.logEvent(msg);
    }
}

输出:

 1 testValue event [1 testKey="testValue"] message
EVENT 1 testValue 
    event [1 testKey="testValue"] message

请注意,eventappender 正确地sd从 StructuredDataMessage 中取消引用键。

但是,以下内容在带有 pax-logging 的 OSGi中不起作用:

org.ops4j.pax.logging.cfg:

log4j2.appender.console.type = Console
log4j2.appender.console.name = STDOUT
log4j2.appender.console.layout.type = PatternLayout
log4j2.appender.console.layout.pattern = %m%n

log4j2.appender.event.type = Console
log4j2.appender.event.name = event
log4j2.appender.event.layout.type = PatternLayout
log4j2.appender.event.layout.pattern = %marker \$\\\{sd:id\} \$\\\{sd:testKey\} %n    %m%n

log4j2.rootLogger.level = debug
log4j2.rootLogger.appenderRef.console.ref = STDOUT

log4j2.logger.event.name = EventLogger
log4j2.logger.event.level = debug
log4j2.logger.event.appenderRef.console.ref = event
log4j2.logger.event.additivity = false

测试.java:

public class Test implements BundleActivator {

    private static final Logger LOGGER = LogManager.getLogger(Test.class);

    @Override
    public void start(BundleContext context) throws Exception {
        StructuredDataMessage msg = new StructuredDataMessage("1", "message", "event");
        msg.put("testKey", "testValue");

        LOGGER.info(msg);
        EventLogger.logEvent(msg, Level.INFO);
    }

    @Override
    public void stop(BundleContext context) throws Exception {
    }
}

输出:

event [1 testKey="testValue"] message
EVENT ${sd:id} ${sd:testKey}
    event [1 testKey="testValue"] message

有什么技巧可以让它在 pax-logging 中工作吗?我可以\$\\\{ctx:key\}在适用时从 MDC 访问值,所以我假设语法是相似的。我还尝试使用 RoutingAppender、FileAppender 等模式中的查找,但无济于事。

提前致谢!

编辑:我正在使用最新版本的 pax-logging-api 和 pax-logging-log4j2 (1.11.3)

4

1 回答 1

1

好的,这还不是一个明确的答案——简单的评论太短了,无法描述发生了什么。

您调用的堆栈跟踪是:

"pipe-restart 238@10666" prio=5 tid=0xc3 nid=NA runnable
  java.lang.Thread.State: RUNNABLE
      at org.ops4j.pax.logging.log4j2.internal.PaxLoggerImpl.doLog0(PaxLoggerImpl.java:354)
      at org.ops4j.pax.logging.log4j2.internal.PaxLoggerImpl.doLog(PaxLoggerImpl.java:337)
      at org.ops4j.pax.logging.log4j2.internal.PaxLoggerImpl.inform(PaxLoggerImpl.java:233)
      at org.ops4j.pax.logging.internal.TrackingLogger.inform(TrackingLogger.java:209)
      at org.ops4j.pax.logging.log4jv2.Log4jv2Logger.logMessage(Log4jv2Logger.java:162)
      at org.apache.logging.log4j.spi.AbstractLogger.log(AbstractLogger.java:2102)
      at org.apache.logging.log4j.spi.AbstractLogger.tryLogMessage(AbstractLogger.java:2190)
      at org.apache.logging.log4j.spi.AbstractLogger.logMessageTrackRecursion(AbstractLogger.java:2144)
      at org.apache.logging.log4j.spi.AbstractLogger.logMessageSafely(AbstractLogger.java:2127)
      at org.apache.logging.log4j.spi.AbstractLogger.logIfEnabled(AbstractLogger.java:1828)
      at org.apache.logging.log4j.EventLogger.logEvent(EventLogger.java:56)
      at grgr.test.ActivatorLogging.start(ActivatorLogging.java:39)
...

org.ops4j.pax.logging.log4jv2.Log4jv2Logger.logMessage()是日志外观日志后端之间的桥梁。

请记住 - 使用 pax-logging,您可以将 Commons Logging外观与 Log4J1后端一起使用,或者将 Log4j2外观(这就是您正在做的事情)与例如 Logback后端一起使用。

这就是为什么org.ops4j.pax.logging.log4jv2.Log4jv2Logger.logMessage()这样做:

} else if (level.intLevel() >= Level.INFO.intLevel()) {
    m_delegate.inform(paxMarker, message.getFormattedMessage(), t, fqcn);

并且您的结构化消息更改为 String event [1 testKey="testValue"] message

只有这样配置的附加程序才会被调用 - 并且具有提取结构化数据的布局的附加程序无法找到它,因为结构化消息已经转换为纯字符串。

这 3 行:

  at org.ops4j.pax.logging.log4j2.internal.PaxLoggerImpl.inform(PaxLoggerImpl.java:233)
  at org.ops4j.pax.logging.internal.TrackingLogger.inform(TrackingLogger.java:209)
  at org.ops4j.pax.logging.log4jv2.Log4jv2Logger.logMessage(Log4jv2Logger.java:162)

从 pax-logging-api (facade) 通过(bridge) 到 pax-logging-log4j2 (backend) 之间的交叉TrackingLogger丢失结构化信息。

我已经创建了https://ops4j1.jira.com/browse/PAXLOGGING-302并希望尽快做点什么。

编辑1

关键是在 中org.apache.logging.log4j.core.lookup.StructuredDataLookup#lookup(),这个条件为真:

if (event == null || !(event.getMessage() instanceof StructuredDataMessage)) {
    return null;
}

编辑2

我刚刚修复了https://ops4j1.jira.com/browse/PAXLOGGING-302,这个测试证明它有效:

Logger logger = LogManager.getLogger("my.logger");

logger.info(new StructuredDataMessage("1", "hello!", "typeX").with("key1", "sd1"));
logger.info(new StringMapMessage().with("key1", "map1"));

List<String> lines = readLines();
assertTrue(lines.contains("my.logger/org.ops4j.pax.logging.it.Log4J2MessagesIntegrationTest typeX/sd1 [INFO] typeX [1 key1=\"sd1\"] hello!"));
assertTrue(lines.contains("my.logger/org.ops4j.pax.logging.it.Log4J2MessagesIntegrationTest ${sd:type}/map1 [INFO] key1=\"map1\""));

配置是:

log4j2.appender.console.type = Console
log4j2.appender.console.name = console
log4j2.appender.console.layout.type = PatternLayout
log4j2.appender.console.layout.pattern = %c/%C ${sd:type}/${map:key1} [%p] %m%n
log4j2.rootLogger.level = info
log4j2.rootLogger.appenderRef.file.ref = console

etc/org.ops4j.pax.logging.cfg(如果在 Karaf 中配置,则必须使用您使用过的转义序列)。

于 2019-11-15T08:09:33.357 回答