ASF GitHub Bot commented on NIFI-4809:

Github user mattyb149 commented on a diff in the pull request:

    --- Diff: 
    @@ -140,8 +164,16 @@
    +    static final PropertyDescriptor RECORD_WRITER = new 
    +            .name("record-writer")
    +            .displayName("Record Writer")
    +            .description("Specifies the Controller Service to use for 
writing out the records.")
    --- End diff --
    The description here should mention that it is only used when the reporting 
task is configured to use a Record Writer. For the one you added, it has two 
modes, but future reporting tasks need not offer an alternative.

> 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 
> 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

Reply via email to