[
https://issues.apache.org/jira/browse/NIFI-6780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957023#comment-16957023
]
ASF subversion and git services commented on NIFI-6780:
-------------------------------------------------------
Commit ace23c35b5f5c298af64e5bd6aa62c797cecc4fc in nifi's branch
refs/heads/master from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=ace23c3 ]
NIFI-6780: Add QueryNiFiReportingTask, RecordSinkService, S2S and DB impls
(#3826)
* NIFI-6780: Introduce RecordSinkService to separate format and destination,
refactor common S2S utils
Added QueryNiFiReportingTask to SQL query NiFi status and metrics
Add PROCESSOR_STATUS and PROCESS_GROUP_STATUS
Add CONNECTION_STATUS_PREDICTIONS
check for null predictions
Add ConnectionStatusRecursiveIterator
Fix issue w/ duplicate iterator outputs
Refactored query interfaces, fixed assembly POM
Rebased v master, fixed isBackPressureEnabled and Checkstyle/RAT errors
Add DatabaseRecordSink service (#13)
* Add DatabaseRecordSink service
* Incorporated review comments
* NIFI-6780: Add/fix docs, cleanup warnings, fixed some table definitions
* Added bundle profile, remove predictions table if not enabled
* Added doc for which tables are available when
This closes #3826.
> 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
> 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)
