You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2015/11/07 04:11:10 UTC

[jira] [Updated] (NIFI-636) Processor Logger methods should use configured logging levels for message and throwable

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

Joseph Witt updated NIFI-636:
-----------------------------
    Fix Version/s:     (was: 0.4.0)

> Processor Logger methods should use configured logging levels for message and throwable
> ---------------------------------------------------------------------------------------
>
>                 Key: NIFI-636
>                 URL: https://issues.apache.org/jira/browse/NIFI-636
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>    Affects Versions: 0.1.0
>            Reporter: Brian Ghigiarelli
>            Priority: Minor
>              Labels: beginner, newbie
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The SimpleProcessLogger and MockProcessorLog accept messages, parameters, and throwables to match the SLF4J interface, but throwables are only logged if DEBUG is enabled for the particular category, regardless of the level of the log method.
> As indicated on the developer mailing list, this was intended to reduce the verbosity of the logs by only including stack traces for those who were debugging the system.  With the general shift toward provenance as an operational utility instead of log files, NiFi should support consistent logging of messages and throwables at the levels configured in the system.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)