[ https://issues.apache.org/jira/browse/NIFI-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16339588#comment-16339588 ]
ASF GitHub Bot commented on NIFI-4814: -------------------------------------- Github user mattyb149 commented on the issue: https://github.com/apache/nifi/pull/2431 Also, not required but it might be a good idea to add the type as well. Either way, let me know and I'll merge > Add distinctive attribute to S2S reporting tasks > ------------------------------------------------ > > Key: NIFI-4814 > URL: https://issues.apache.org/jira/browse/NIFI-4814 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions > Reporter: Pierre Villard > Assignee: Pierre Villard > Priority: Major > > I'm currently using multiple S2S reporting tasks to send various monitoring > data about my workflows. However this forces me to use multiple input ports > (one per type of reporting task) as I'm not able to easily distinct what data > comes from what reporting task. > I'd like to add an attribute "reporting.task.name" set to the name of the > reporting task when sending flow files via S2S. This way I can use a single > input port and then use a RouteOnAttribute processor to split my data based > on the reporting task source. The objective to use a single input port is to > reduce the number of threads used for S2S operations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)