[
https://issues.apache.org/jira/browse/PIRK-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427304#comment-15427304
]
ASF GitHub Bot commented on PIRK-54:
------------------------------------
Github user ellisonanne commented on the issue:
https://github.com/apache/incubator-pirk/pull/71
```
Levels used for identifying the severity of an event. Levels are organized
from most specific to least:
OFF (most specific, no logging)
FATAL (most specific, little data)
ERROR
WARN
INFO
DEBUG
TRACE (least specific, a lot of data)
ALL (least specific, all data)
Typically, configuring a level in a filter or on a logger will cause
logging events of that level and those that are more specific to pass through
the filter. A special level, ALL, is guaranteed to capture all levels when used
in logging configurations.
```
https://logging.apache.org/log4j/2.0/log4j-api/apidocs/org/apache/logging/log4j/Level.html
> Log Levels Not Functioning
> --------------------------
>
> Key: PIRK-54
> URL: https://issues.apache.org/jira/browse/PIRK-54
> Project: PIRK
> Issue Type: Bug
> Affects Versions: 0.0.1
> Reporter: Ellison Anne Williams
> Fix For: 0.1.0
>
>
> The log levels in the log4j2.xml file do not appear to be working. Currently,
> setting
> <Root level="debug">
> <AppenderRef ref="STDOUT"/>
> <AppenderRef ref="RollingFile"/>
> </Root>
> doesn't cause any debug output (only info)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
