You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Behrouz (Jira)" <ji...@apache.org> on 2020/01/28 20:43:00 UTC

[jira] [Commented] (NIFI-6780) Create a Metrics Query Reporting Task

    [ https://issues.apache.org/jira/browse/NIFI-6780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17025431#comment-17025431 ] 

Behrouz commented on NIFI-6780:
-------------------------------

Could you please give us an example how to use this service. It would be better if you write an article with some examples.

> Create a Metrics Query Reporting Task
> -------------------------------------
>
>                 Key: NIFI-6780
>                 URL: https://issues.apache.org/jira/browse/NIFI-6780
>             Project: Apache NiFi
>          Issue Type: New Feature
>            Reporter: Yolanda M. Davis
>            Assignee: Matt Burgess
>            Priority: Major
>             Fix For: 1.10.0
>
>          Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> Currently NiFi has metrics reporting tasks which have a specific set of metrics that are sent out to via site-to-site or other protocols. To expand upon this a query based reporting task is proposed to provide users the flexibility to select the types of metrics and the conditions on they should be reported using sql like statements.
>  It may be desired that the results of a query are transmitted to any number of targets. The current pattern is to implement this as a Site-to-Site reporting task, but that puts the onus on the user to create a sub-flow with an Input Port for receiving the S2S messages, and it creates additional provenance events for these. A new approach to be considered here is to decouple the results from the destination. Proposed is a RecordSinkService controller service interface, which the query-based reporting task uses to transmit the query results. The configured RecordSinkService implementation would be responsible for the actual transmission of results to the sink. Possible initial implementations include a Site-To-Site RecordSink (for feature parity with the other reporting tasks) and a DatabaseRecordSink (to transmit the query results to an external RDBMS using DBCPConnectionPool).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)