When using log4j AsyncLoggerContextSelector , trace.id and transaction.id is not injected into the MDC context

Elastic Observability Logs
, ,
1

Hi , we are setting -DLog4jContextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector in our jvm proprties and using elastic agent version 1.42.0 .
When using the above mentioned log4j async context selector , we are not getting trace.id and transaction.id in the MDC context.

But when we remove the above jvm arg , it works fine.
Is there any solution for it?

2

Hi,

Unfortunately this is not supported, and we already have an issue to implement this: Add instrumentation for Log4j2 with AsyncLoggerContextSelector that enables log correlation · Issue #3132 · elastic/apm-agent-java · GitHub

Make sure to subscribe to the issue notifications to know when progress is made on this.

For now, it's not in our short-term roadmap, thus there is no ETA when this will be implemented.

3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.