THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| Page properties | ||
|---|---|---|
|
Status
Current state: Under DiscussionRejected
Discussion thread: https://lists.apache.org/thread/n8omkpjf1mk9jphx38b8tfrs4h3nxo3z
...
Here is the table of the corresponding native levels of all the supported logging implementations.
Level / Implementation | Log4j | Logback | Java Logging |
|---|---|---|---|
TRACE | org.apache.logging.log4j.Level.TRACE | ch.qos.logback.classic.TRACE | java.util.logging.FINEST |
| org.apache.logging.log4j.Level.DEBUG | ch.qos.logback.classic.DEBUG | java.util.logging.FINE |
INFO | org.apache.logging.log4j.Level.INFO | ch.qos.logback.classic.INFO | java.util.logging.INFO |
WARN | org.apache.logging.log4j.Level.WARN | ch.qos.logback.classic.WARN | java.util.logging.WARNING |
ERROR | org.apache.logging.log4j.Level.ERROR | ch.qos.logback.classic.ERROR | java.util.logging.SEVERE |
SEVERE | org.apache.logging.log4j.Level.ERROR | ch.qos.logback.classic.ERROR | java.util.logging.SEVERE |
OFF | org.apache.logging.log4j.Level.OFF | ch.qos.logback.classic.OFF | java.util.logging.OFF |
Limitations
Considered to be an MVP (Minimal Viable Product), this improvement does not support the features, such as defining the scope (e.g. job manager or task manager only) and a timer. The log levels of the target logger are going to be changed cluster-wide, on the job manager leader and all the currently-registered task managers. To unset the previously-changed level, pass a null log-level argument.
...