[
https://issues.apache.org/jira/browse/NIFI-5941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard resolved NIFI-5941.
----------------------------------
Resolution: Feedback Received
Apache NiFi 1.x is no longer maintained and no new release is planned on the
1.x release line. Marking as resolved as part of a cleanup operation. Please
open a new one with an updated description if this is still relevant for NiFi
2.x.
> 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
(v8.20.10#820010)
