[
https://issues.apache.org/jira/browse/NIFI-790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14695420#comment-14695420
]
Bryan Bende commented on NIFI-790:
----------------------------------
It would definitely be very cool to visualize metrics per component, as
configured in the reporting task.
I am not 100% sure if this is possible given how Ambari requires the metrics to
be defined up-front. There is one example in the existing Ambari services which
looks like it is attempting to do dynamic metric names, however I have not been
able to get the same approach to work. The scenario I was trying was to send
over GC metrics without knowing the name of the garbage collectors ahead of
time.
I sent a question to the Ambari user list about how to make this work, will
report back if/when I know more.
> 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)
