[
https://issues.apache.org/jira/browse/NIFI-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15750168#comment-15750168
]
Andrew Psaltis commented on NIFI-3196:
--------------------------------------
It would certainly be possible to put other processors in-front of this to do
transformation of the data. The only thing this knows about the input is that
it is a MiNiFi FlowStatus report serialized as JSON and from that it
deserializes it and sends it along as metrics to AAI.
> Provide MiNiFi FlowStatus Insights processor that integrates MiNiFi Flow
> Status Report with Azure Application Insights
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-3196
> URL: https://issues.apache.org/jira/browse/NIFI-3196
> Project: Apache NiFi
> Issue Type: New Feature
> Affects Versions: 1.1.0
> Reporter: Andrew Psaltis
> Assignee: Andrew Psaltis
>
> As a user of both NiFi and MiNiFi there are many times I would like to have
> an operational dashboard for MiNiFi. Although, there is a discussion and
> desire for [Centralized management |
> https://cwiki.apache.org/confluence/display/MINIFI/MiNiFi+Community+Driven+Requirements]
> there are many times where as a user I just want to be able to use the
> operational tools I already have. In many cases those may be products such
> as: Nagios, Zenoos, Zabix, Graphite, Grafana and in cloud environments
> perhaps Azure Application Insights and AWS Cloudwatch.
> This JIRA and the related P/R provides a processor that ingests the MiNiFi
> Flow Status report and sends it to Azure Application Insights as custom
> metrics. This then allows a user to set alerts in Azure Application Insights,
> thus providing the ability to monitor MiNiFi agents. As such, this has a
> dependency on the following MiNiFi JIRA: [Change FlowStatusReport to be JSON
> | https://issues.apache.org/jira/browse/MINIFI-170]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
