You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by apsaltis <gi...@git.apache.org> on 2016/12/15 01:30:33 UTC
[GitHub] nifi pull request #1331: NIFI-3196 Provide MiNiFi FlowStatus Insights proces...
GitHub user apsaltis opened a pull request:
https://github.com/apache/nifi/pull/1331
NIFI-3196 Provide MiNiFi FlowStatus Insights processor that integrates MiNiFi Flow Status Report with Azure Application Insights
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 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 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://github.com/apache/nifi-minifi/pull/65](url))
An example flow of how to set this up for the MiNiFi side is:
And the NiFi Side looks like:
Then once this is all set in Azure Application Insights I can build a dashboard that may look like this:
And explore all the various metrics, that I may want to build a dashboard from:
I can then also go and set alerts
In the end this type of integration can also be done with other enterprise tools.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apsaltis/nifi NIFI-3196
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1331.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1331
----
commit 9d3fa636a4f0feb9c7055488c5f686dd3f237e36
Author: Andrew Psaltis <ps...@gmail.com>
Date: 2016-12-14T16:40:27Z
NIFI-3196 Provide MiNiFi FlowStatus Insights processor that integrates MiNiFi Flow Status Report with Azure Application Insights
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] nifi issue #1331: NIFI-3196 Provide MiNiFi FlowStatus Insights processor tha...
Posted by jzonthemtn <gi...@git.apache.org>.
Github user jzonthemtn commented on the issue:
https://github.com/apache/nifi/pull/1331
@apsaltis Just found this and I'm glad I did. It looks very nice. I'm facing the same type of task except with AWS CloudWatch. I wanted to ask if you are still continuing development toward what was discussed earlier in this conversation? Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] nifi issue #1331: NIFI-3196 Provide MiNiFi FlowStatus Insights processor tha...
Posted by apsaltis <gi...@git.apache.org>.
Github user apsaltis commented on the issue:
https://github.com/apache/nifi/pull/1331
@trixpan I agree that having something much more generic would be great. I am totally open to closing this PR, rebasing my branch and taking this processor in that direction. Honestly, after having time to think about it It being tied to MiNiFi and talking with others I totally agree.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] nifi issue #1331: NIFI-3196 Provide MiNiFi FlowStatus Insights processor tha...
Posted by trixpan <gi...@git.apache.org>.
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/1331
@apsaltis - loved the idea behind this contribution - I'm also very much in favor of fitting MiNiFi with existing systems - and perhaps that's the reason for my first question:
Is there a reason why to bundle the Azure Insights as a bundle tied to this NAR? Looking at the metrics collected it seems fairly useful to NiFi as well and suspect people running NiFi in the cloud would rave about being able to send reporting data directly into insights instead of having to rely solely on Ambari and other existing reporting services.
It may be just me but I suspect AzureApplicationInsights if empowered by Expression Language enabled Dynamic Properties would be a killing processor...
What do you think?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] nifi issue #1331: NIFI-3196 Provide MiNiFi FlowStatus Insights processor tha...
Posted by trixpan <gi...@git.apache.org>.
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/1331
@apsaltis - glad comments were helpful.
New PR or not, the work is truly great and I can confess that with the exception of Azure components I will very likely be using it the outcome of the new contribution as soon as it gets merged. :-)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---