You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please offer a option to activate just one Wrapper or set a preference order (1 JBoss Logmanager, 2 slf4j, 3 log4j2, 4 log4j12)
The text was updated successfully, but these errors were encountered:
bunckelvhv
changed the title
WildFly Logging SubSystem MDC turned on/off per Thread
WildFly Logging SubSystem MDC called multiple times
Jun 11, 2020
JonasKunz
changed the title
WildFly Logging SubSystem MDC called multiple times
Add an opt-out configuration option for each MDC integration
Jun 29, 2020
JonasKunz
added a commit
to JonasKunz/inspectit-ocelot
that referenced
this issue
Jun 29, 2020
WildFly's logging system is based on JBoss Logmanager. Additionally it ships several JBoss specific wrappers for major logging APIs
https://github.com/wildfly/wildfly-core/blob/master/pom.xml
Additionally a Logj4j2 Implementation pointing to JBoss Logmanager is available.
https://github.com/inspectIT/inspectit-ocelot/blob/master/inspectit-ocelot-core/src/main/java/rocks/inspectit/ocelot/core/instrumentation/correlation/log/MDCAccess.java
currently registers all of them at the same time.
There is no option to activate just one of the MDC Wrappers. In case of WildFly one MDC call would reach the same implementation multiple times, causing unnecessary overhead.
Please offer a option to activate just one Wrapper or set a preference order (1 JBoss Logmanager, 2 slf4j, 3 log4j2, 4 log4j12)
The text was updated successfully, but these errors were encountered: