Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Level / ImplementationLog4jLogbackJava Logging
TRACEorg.apache.logging.log4j.Level.TRACEch.qos.logback.classic.TRACEjava.util.logging.FINEST

DEBUG

org.apache.logging.log4j.Level.DEBUGch.qos.logback.classic.DEBUGjava.util.logging.FINE
INFOorg.apache.logging.log4j.Level.INFOch.qos.logback.classic.INFOjava.util.logging.INFO
WARNorg.apache.logging.log4j.Level.WARNch.qos.logback.classic.WARNjava.util.logging.WARNING
ERRORorg.apache.logging.log4j.Level.ERRORch.qos.logback.classic.ERRORjava.util.logging.SEVERE
SEVEREorg.apache.logging.log4j.Level.ERRORch.qos.logback.classic.ERRORjava.util.logging.SEVERE
OFForg.apache.logging.log4j.Level.OFFch.qos.logback.classic.OFFjava.util.logging.OFF

Limitations

TBDConsidered 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.


Compatibility, Deprecation, and Migration Plan

...