[ https://issues.apache.org/jira/browse/NIFI-5941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16739545#comment-16739545 ]
Michael Moser commented on NIFI-5941: ------------------------------------- You're correct [~coffeethulhu], it's not a good user experience to require a logback.xml change in order to log DEBUG or TRACE level messages from this processor. I would recommend in this case that we change the default [logback.xml|https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-resources/src/main/resources/conf/logback.xml#L89] to allow TRACE level messages from both LogMessage and LogAttribute. > LogMessage routes to nonexistent failure when log level is below logback > allowed > -------------------------------------------------------------------------------- > > Key: NIFI-5941 > URL: https://issues.apache.org/jira/browse/NIFI-5941 > Project: Apache NiFi > Issue Type: Bug > Affects Versions: 1.7.0, 1.8.0, 1.7.1 > Reporter: Matthew Dinep > Priority: Major > > When using the LogMessage processor, if a message is configured to log at a > level that is below what is set in logback.xml (for example logging at "info" > when the default log level is "warn"), the message doesn't get logged and an > error is thrown because the flowfile is unable to be routed to failure (the > only available route on the processor is Success). Since this is a user > configurable log level for a specific case, the level for the message should > be able to override the global log level in logback.xml so as to avoid this > behavior. -- This message was sent by Atlassian JIRA (v7.6.3#76005)