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
The Log4j system property `log4j2.defaultStatusLevel` has almost the
same purpose as the `log4j2.statusLoggerLevel`:
* the `log4j2.statusLoggerLevel` property sets the level of the fallback
status logger listener **before** a configuration is parsed,
* the `log4j2.defaultStatusLevel` property sets the level of the
fallback status logger listener **after** a configuration is parsed
(unless the configuration has a `status` attribute).
Removing one of them makes `-Dlog4j2.statusLoggerLevel=WARN` a viable
less verbose alternative to `-Dlog4j2.debug`.
Since StatusLogger implements the Log4j 2 API's Logger interface, all
1716
1716
the normal Logger methods may be used.
1717
1717
1718
-
When configuring Log4j it is sometimes necessary to view the generated
1719
-
status events. This can be accomplished by adding the status attribute
1720
-
to the configuration element or a default value can be provided by
1721
-
setting the "Log4jDefaultStatusLevel" system property. Valid values of
1722
-
the status attribute are "trace", "debug", "info", "warn", "error" and
1723
-
"fatal". The following configuration has the status attribute set to
1724
-
debug.
1718
+
When configuring Log4j it is sometimes necessary to view the generated status events.
1719
+
This can be accomplished by adding the status attribute to the configuration element or a default value can be provided by setting the xref:statusLoggerLevel["log4j2.statusLoggerLevel"] system property.
1720
+
Valid values of the status attribute are "trace", "debug", "info", "warn", "error" and "fatal".
1721
+
The following configuration has the status attribute set to debug.
1725
1722
1726
1723
[source,xml]
1727
1724
----
@@ -2219,18 +2216,6 @@ The following is a list of available global configuration properties. Note that
2219
2216
until a listener is registered. In practice, a listener is registered when a configuration is found,
2220
2217
and from that point onwards, status messages are only sent to the listeners (depending on their statusLevel).
0 commit comments