[
https://issues.apache.org/jira/browse/NIFI-4809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16339402#comment-16339402
]
ASF GitHub Bot commented on NIFI-4809:
--------------------------------------
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/2430
Reusing the Ambari format certainly makes this one easier to implement, and
as you said the user can convert later with a record processor, but I'm
thinking it might be best to be able to specify the RecordWriter in the
reporting task. That way the conversion, filtering, etc. can be done while the
records are already in object format (i.e. parsed), which would save the step
of re-parsing and re-writing. Using a JsonRecordSetWriter with "Inherit Record
Schema" would result in the same behavior as you propose here, or you could
provide a different format and/or filter out the fields, etc. by using a
configured RecordSetWriter.
@markap14 suggested to encode the "input" schema as a file in
src/main/resources and read it in when the class/instance is created, using the
available util method to convert it to a RecordSchema. To be honest I would
like to have the S2S Provenance reporting task do this as well, but that's a
bit more invasive since it already exists. Since the one in this PR is new,
would be nice to have it be the exemplar for creating reporting services in the
future. What do you think?
> Implement a SiteToSiteMetricsReportingTask
> ------------------------------------------
>
> Key: NIFI-4809
> URL: https://issues.apache.org/jira/browse/NIFI-4809
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Major
>
> At the moment there is an AmbariReportingTask to send the NiFi-related
> metrics of the host to the Ambari Metrics Service. In a multi-cluster
> configuration, or when working with MiNiFi (Java) agents, it might not be
> possible for all the NiFi instances (NiFi and/or MiNiFi) to access the AMS
> REST API.
> To solve this problem, a solution would be to implement a
> SiteToSiteMetricsReportingTask to send the data via S2S to the "main" NiFi
> instance/cluster that will be able to publish the metrics into AMS (using
> InvokeHTTP). This way, it is possible to have the metrics of all the
> instances exposed in one AMS instance.
> I propose to send the data formatted as we are doing right now in the Ambari
> reporting task. If needed, it can be easily converted into another schema
> using the record processors once received via S2S.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
