[
https://issues.apache.org/jira/browse/NIFI-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15748789#comment-15748789
]
Aldrin Piri commented on NIFI-3196:
-----------------------------------
Sounds like a good concept. Curious if it makes sense to deconstruct this a
bit more but do not have great familiarity with the Azure App Insights (AAI).
Could see a series of processors that receive the data, then transform
(transform JSON) and then a PutAAI or similar. That last bit of functionality
seems like it might get some nice reuse for a lot of other uses.
> 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)
