[
https://issues.apache.org/jira/browse/NIFI-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16539999#comment-16539999
]
ASF GitHub Bot commented on NIFI-5407:
--------------------------------------
Github user pvillard31 commented on the issue:
https://github.com/apache/nifi/pull/2877
Hi @richmidwinter - usually we recommend to use the Site To Site Reporting
tasks to re-ingest data generated by NiFi at framework level (such as
controller status, bulletins, provenance events, etc) as flow files so you can
use the existing processors to do whatever you want with this data. In your
case you'd have the SiteToSiteControllerStatusReportingTask sending the data to
an InputPort at the root level of the canvas and you would then use one of the
Elasticsearch processor to send the data to ES. You can have a look here:
https://pierrevillard.com/2017/05/13/monitoring-nifi-site2site-reporting-tasks/
Not saying that we don't want the reporting task you created, it's just
that this reporting task is probably tied to a specific ES version and would
need to be updated if new ES versions introduce major changes.
Let me know what you think.
> Add a MetricsReportingTask to send to ElasticSearch
> ---------------------------------------------------
>
> Key: NIFI-5407
> URL: https://issues.apache.org/jira/browse/NIFI-5407
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 1.7.0
> Reporter: rich
> Priority: Trivial
>
> As far as I can tell, there isn't a MetricsReportingTask which persists to
> Elastic.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
