You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Matthew Dinep (JIRA)" <ji...@apache.org> on 2019/01/10 00:55:00 UTC

[jira] [Updated] (NIFI-5941) LogMessage routes to nonexistent failure when log level is below logback allowed

     [ https://issues.apache.org/jira/browse/NIFI-5941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthew Dinep updated NIFI-5941:
--------------------------------
    Affects Version/s: 1.8.0

> 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)