Github user rickysaltzer commented on the pull request:
https://github.com/apache/nifi/pull/91#issuecomment-149875162
@busbey good question. I envision that we can later extend the Riemann
bundle to allow internal NiFi reporting to Riemann, similar to how Ambari was
recently added. For now, there are plenty of situations where it would be
useful to allow reporting of a flowfile's existence and/or attributes to
Riemann for basic data flow reporting and monitoring.
Let me give you a few examples:
* Send a notification to Riemann for each flowfile passed through a
specific processor. This not only allows for monitoring, but also alerting if
desired.
* Each node in the NiFi cluster can periodically send a message with a TTL
that if expires would indicate that the node in the cluster is no longer
running.
* Immediate alerting when specific data flow scenarios are met (e.g. failed
to extract archive, failed to hit an API).
* To extend on what @trkurc said, you could very easily report metrics from
files if desired. Or - you could use the ExecuteProcess to collect metrics
using arbitrary commands.
I'm sure there are other use cases that can be applied.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
