[
https://issues.apache.org/jira/browse/NIFI-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Gresock updated NIFI-3674:
---------------------------------
Description:
I would like to see a reporting task similar to
SiteToSiteProvenanceReportingTask that sends controller status events using
JSON over S2S. Since the ProcessGroupStatus object structure is recursive,
ideally the JSON structure would be flat, with references to parentIds embedded.
This would allow status history to be stored using any arbitrary mechanism.
Other interesting features would include:
* Properties to filter which components to include (Process Group, Processor,
Input/Output Ports, Remote Process Group, Connection)
* Properties to filter by regex which component names or ids to include in the
output
was:
I would like to see a reporting task similar to
SiteToSiteProvenanceReportingTask that sends controller status events using
JSON over S2S. Since the ProcessGroupStatus object structure is recursive,
ideally the JSON structure would be flat, with references to parentIds embedded.
This would allow status history to be stored using any arbitrary mechanism.
Other interesting features would include:
* Properties to filter which components to include (Process Group, Processor,
Input/Output Ports, Remote Process Group)
* Properties to filter by regex which component names or ids to include in the
output
> Implement SiteToSiteStatusReportingTask
> ---------------------------------------
>
> Key: NIFI-3674
> URL: https://issues.apache.org/jira/browse/NIFI-3674
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Joseph Gresock
> Priority: Minor
> Labels: Site-to-Site, reporting_task, status
>
> I would like to see a reporting task similar to
> SiteToSiteProvenanceReportingTask that sends controller status events using
> JSON over S2S. Since the ProcessGroupStatus object structure is recursive,
> ideally the JSON structure would be flat, with references to parentIds
> embedded.
> This would allow status history to be stored using any arbitrary mechanism.
> Other interesting features would include:
> * Properties to filter which components to include (Process Group, Processor,
> Input/Output Ports, Remote Process Group, Connection)
> * Properties to filter by regex which component names or ids to include in
> the output
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
