[
https://issues.apache.org/jira/browse/NIFI-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16280089#comment-16280089
]
Anmol Prakash Gautam commented on NIFI-3877:
--------------------------------------------
Hi [~pvillard] - Is there any update or workaround to solve this logging
challenge? We are starting to use Nifi and have run into similar challenge with
logging where we want to know which pipeline a processor belonged to in case of
any error/issue.
> Improve log messages using processor name
> -----------------------------------------
>
> Key: NIFI-3877
> URL: https://issues.apache.org/jira/browse/NIFI-3877
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Pierre Villard
> Priority: Minor
>
> Right now log messages from processors will have the following format:
> {noformat}
> 2017-05-12 10:43:37,780 INFO [Timer-Driven Process Thread-4]
> o.a.nifi.processors.standard.InvokeHTTP
> InvokeHTTP[id=f7ebb153-015b-1000-f590-599786e16340] <log message>
> {noformat}
> We have twice the information of the class name. Could be useful (in
> multi-tenant context) to have the processor name. If the processor is named
> "MyProcessor", we'd have something like:
> {noformat}
> 2017-05-12 10:43:37,780 INFO [Timer-Driven Process Thread-4]
> o.a.nifi.processors.standard.InvokeHTTP
> MyProcessor[id=f7ebb153-015b-1000-f590-599786e16340] <log message>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
