[ 
https://issues.apache.org/jira/browse/NIFI-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14561042#comment-14561042
 ] 

ASF GitHub Bot commented on NIFI-636:
-------------------------------------

Github user brianghig commented on the pull request:

    https://github.com/apache/incubator-nifi/pull/59#issuecomment-105926818
  
    @danbress - I created NIFI-636 to cover this PR, and updated the PR's title 
to link it.
    
    @joewitt - the use case I'm considering for stack traces is operational 
with feedback to engineering teams. When something is going wrong on some far 
away network, we've had folks and/or tools tailing logs and reporting details 
about the errors to dev teams via tickets that include stack traces.  
Additionally, stack traces can be useful tools for low-level auditing purposes 
to follow the flow of a user or piece of data through layers of the system, but 
as you've said, provenance does a much better job of handling that.


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

Reply via email to