[
https://issues.apache.org/jira/browse/NIFI-5941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael W Moser reassigned NIFI-5941:
-------------------------------------
Affects Version/s: (was: 1.8.0)
(was: 1.7.1)
Assignee: Michael W Moser
Description: 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. (was: 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.)
Priority: Minor (was: Major)
Summary: LogMessage drops message when log level is below logback
allowed (was: LogMessage routes to nonexistent failure when log level is below
logback allowed)
> 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
>
> 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)
