[
https://issues.apache.org/jira/browse/NIFI-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15076630#comment-15076630
]
Ricky Saltzer commented on NIFI-1337:
-------------------------------------
I have a pretty decent proof of concept version working that's largely based on
the work from the {{AmbariReportingTask}}. I'm able to successfully report
metrics to a local Riemann instance on a 1 second interval. In addition to
overall NiFi flow metrics and JVM metrics, I'm also reporting individual
processor metrics. The service name format is still up in the air, but for now
it looks like the following:
*Overall NiFi Data Flow Metrics*
{{<user-defined-prefix>.<data-flow-name>.<metric>}}
*Individual Processor Metrics*
{{<user-defined-prefix>.<processor-type>.<processor-id>.<metric>}}
*JVM Metrics*
{{<user-defined-prefix>.jvm.<metric>}}
*Example Data Flow*
{{GenerateFlowFile}} -> {{PutFile}} -> {{UpdateAttribute}}
|nifi-test.GenerateFlowFile.12a3da13-41eb-48ec-8851-af954f7cfe52.active.threads|0.0|
|nifi-test.GenerateFlowFile.12a3da13-41eb-48ec-8851-af954f7cfe52.average.lineage.duration.ms.last-5-minutes|20.0|
|nifi-test.GenerateFlowFile.12a3da13-41eb-48ec-8851-af954f7cfe52.bytes.queued|0.0|
|nifi-test.GenerateFlowFile.12a3da13-41eb-48ec-8851-af954f7cfe52.bytes.read.last-5-minutes|0.0|
|nifi-test.GenerateFlowFile.12a3da13-41eb-48ec-8851-af954f7cfe52.bytes.received.last-5-minutes|0.0|
|nifi-test.GenerateFlowFile.12a3da13-41eb-48ec-8851-af954f7cfe52.bytes.sent.last-5-minutes|0.0|
|nifi-test.GenerateFlowFile.12a3da13-41eb-48ec-8851-af954f7cfe52.bytes.written.last-5-minutes|170086400.0|
|nifi-test.GenerateFlowFile.12a3da13-41eb-48ec-8851-af954f7cfe52.flowfiles.received.last-5-minutes|0.0|
|nifi-test.GenerateFlowFile.12a3da13-41eb-48ec-8851-af954f7cfe52.flowfiles.sent.last-5-minutes|16610.0|
|nifi-test.NiFi Flow.active.threads|0.0|
|nifi-test.NiFi Flow.bytes.queued|0.0|
|nifi-test.NiFi Flow.bytes.read.last-5-minutes|170086400.0|
|nifi-test.NiFi Flow.bytes.received.last-5-minutes|0.0|
|nifi-test.NiFi Flow.bytes.sent.last-5-minutes|0.0|
|nifi-test.NiFi Flow.bytes.transferred.last-5-minutes|193955840.0|
|nifi-test.NiFi Flow.bytes.written.last-5-minutes|340172800.0|
|nifi-test.NiFi Flow.flowfiles.queued.count|0.0|
|nifi-test.NiFi Flow.flowfiles.received.last-5-minutes|0.0|
|nifi-test.NiFi Flow.flowfiles.sent.last-5-minutes|0.0|
|nifi-test.NiFi Flow.flowfiles.transferred.last-5-minutes|18941.0|
|nifi-test.NiFi Flow.total.task.duration.seconds|8.33750171648e+11|
|nifi-test.PutFile.cd34a606-fc34-48e4-8091-deed35988bf4.active.threads|0.0|
|nifi-test.PutFile.cd34a606-fc34-48e4-8091-deed35988bf4.average.lineage.duration.ms.last-5-minutes|7828.0|
|nifi-test.PutFile.cd34a606-fc34-48e4-8091-deed35988bf4.bytes.queued|0.0|
|nifi-test.PutFile.cd34a606-fc34-48e4-8091-deed35988bf4.bytes.read.last-5-minutes|170086400.0|
|nifi-test.PutFile.cd34a606-fc34-48e4-8091-deed35988bf4.bytes.received.last-5-minutes|0.0|
|nifi-test.PutFile.cd34a606-fc34-48e4-8091-deed35988bf4.bytes.sent.last-5-minutes|0.0|
|nifi-test.PutFile.cd34a606-fc34-48e4-8091-deed35988bf4.bytes.written.last-5-minutes|170086400.0|
|nifi-test.PutFile.cd34a606-fc34-48e4-8091-deed35988bf4.flowfiles.received.last-5-minutes|16610.0|
|nifi-test.PutFile.cd34a606-fc34-48e4-8091-deed35988bf4.flowfiles.sent.last-5-minutes|16610.0|
|nifi-test.UpdateAttribute.ab1fa61f-efad-4716-8e88-be493b2dab4b.active.threads|0.0|
|nifi-test.UpdateAttribute.ab1fa61f-efad-4716-8e88-be493b2dab4b.average.lineage.duration.ms.last-5-minutes|8050.0|
|nifi-test.UpdateAttribute.ab1fa61f-efad-4716-8e88-be493b2dab4b.bytes.queued|0.0|
|nifi-test.UpdateAttribute.ab1fa61f-efad-4716-8e88-be493b2dab4b.bytes.read.last-5-minutes|0.0|
|nifi-test.UpdateAttribute.ab1fa61f-efad-4716-8e88-be493b2dab4b.bytes.received.last-5-minutes|0.0|
|nifi-test.UpdateAttribute.ab1fa61f-efad-4716-8e88-be493b2dab4b.bytes.sent.last-5-minutes|0.0|
|nifi-test.UpdateAttribute.ab1fa61f-efad-4716-8e88-be493b2dab4b.bytes.written.last-5-minutes|0.0|
|nifi-test.UpdateAttribute.ab1fa61f-efad-4716-8e88-be493b2dab4b.flowfiles.received.last-5-minutes|16610.0|
|nifi-test.UpdateAttribute.ab1fa61f-efad-4716-8e88-be493b2dab4b.flowfiles.sent.last-5-minutes|0.0|
|nifi-test.jvm.daemon_thread_count|21.0|
|nifi-test.jvm.file_descriptor_usage|21.0|
|nifi-test.jvm.gc.runs|55.0|
|nifi-test.jvm.gc.time|277.0|
|nifi-test.jvm.heap_usage|339.0|
|nifi-test.jvm.heap_used|339.0|
|nifi-test.jvm.non_heap_usage|339.0|
|nifi-test.jvm.thread_count|86.0|
|nifi-test.jvm.thread_states.blocked|0.0|
|nifi-test.jvm.thread_states.runnable|30.0|
|nifi-test.jvm.thread_states.terminated|0.0|
|nifi-test.jvm.thread_states.timed_waiting|36.0|
|nifi-test.jvm.uptime|339.0|
> Add Riemann Reporting Task
> --------------------------
>
> Key: NIFI-1337
> URL: https://issues.apache.org/jira/browse/NIFI-1337
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Ricky Saltzer
> Assignee: Ricky Saltzer
>
> It would be beneficial for NiFi to report health information to
> [Riemann|http://riemann.io] for monitoring purposes. I plan on implementing
> this, and will use this JIRA to track the progress.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
