[
https://issues.apache.org/jira/browse/NIFI-5941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18050085#comment-18050085
]
ASF subversion and git services commented on NIFI-5941:
-------------------------------------------------------
Commit fb7dc983263912c429f7e41fc6375fb5f0b7b8e0 in nifi's branch
refs/heads/main from Michael W Moser
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=fb7dc98326 ]
NIFI-5941 set default LogAttribute and LogMessage level to TRACE in logback.xml
to cover all usage scenarios
Signed-off-by: Pierre Villard <[email protected]>
This closes #10728.
> LogMessage drops message 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
> Reporter: Matthew Dinep
> Assignee: Michael W Moser
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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
(v8.20.10#820010)
