[
https://issues.apache.org/jira/browse/NIFI-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15090807#comment-15090807
]
Joseph Witt commented on NIFI-1376:
-----------------------------------
[~rpmiskin] I can see how this is helpful. But want to offer another a
viewpoint. In NiFi we have data provenance and processors can generate these
events. These are a great step beyond logs because they not only have
important information about what happened but they help provide explicit
relationships between what happened. When a processor routes something to any
given relationship they are able to set a description/reason for it.
The logs largely should be for developers at this point. The provenance data
has much more meaning/value/and an integrated user experience for operations
folks. So I'd recommend we make sure to test that more than the logs
themselves. That said, I am supportive of this log testing idea as well. I
just wanted to make sure this other perspective was considered as it is
something that is unique in NiFi.
Thanks
joe
> Provide access to logged messages from TestRunner
> -------------------------------------------------
>
> Key: NIFI-1376
> URL: https://issues.apache.org/jira/browse/NIFI-1376
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 0.4.1
> Reporter: Richard Miskin
> Priority: Minor
> Fix For: 0.5.0
>
>
> It would be useful to be able to verify the log messages raised by Processors
> and ControllerServices during tests.
> As an example use case, imagine a processor with multiple possible errors
> that should cause a flow file to be transferred to a failure Relationship,
> but different messages should be logged.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
