[
https://issues.apache.org/jira/browse/NIFI-790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14695204#comment-14695204
]
Joseph Witt commented on NIFI-790:
----------------------------------
Yes - exactly. Just as a thought it seemed like a good way to handle it would
be that on the configuration for the reporting task the user could add
properties whereby the key of the property becomes the name of the metric group
in Ambari and the value is the identifier of the NiFi component to monitor. So
for example, if there is a processor (could be any component type - processor,
process group, connection) in nifi with the identifier 'abcdef-1234' then the
user would add a property:
key = 'get.tweets'
value = 'abcdef-1234'
Then in Ambari there would be a set of metrics for
get.tweets.flowfilesin5mins
get.tweets.flowfilesout5mins
...
and so on
Ideally we would just send all metrics we have but perhaps this approach is a
good start.
Thanks
Joe
> Create reporting task to deliver metrics to Apache Ambari
> ---------------------------------------------------------
>
> Key: NIFI-790
> URL: https://issues.apache.org/jira/browse/NIFI-790
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Reporter: Joseph Witt
> Assignee: Bryan Bende
> Fix For: 0.3.0
>
> Attachments: NIFI-790.patch
>
>
> Apache Ambari seems to be a good place to aggregate metrics and we're hearing
> from folks that want to use it.
> We should provide a reporting task that makes it extremely simple to send to
> Apache Ambari.
> Probably best to do a simple first pass of basic metrics off high-level flow
> summary stuff. So we can use that to get more detailed feedback on where to
> go with it next. Ambari seems to have a REST API to deliver to.
> https://ambari.apache.org/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
