[
https://issues.apache.org/jira/browse/AMBARI-17027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15314006#comment-15314006
]
Jungtaek Lim edited comment on AMBARI-17027 at 6/3/16 11:38 AM:
----------------------------------------------------------------
Leaving status update here since I cannot assign myself.
I'm working on it: completed work against 2.2.2, will work against trunk.
Please refer this link to see how to use and how output is affected:
https://gist.github.com/HeartSaVioR/04aa5ef2c17b738b2d6533394ff50723
Please let me know if any documentation works are needed.
Thanks in advance!
was (Author: kabhwan):
I'm working on it: completed work against 2.2.2, will work against trunk.
Please refer this link to see how to use and how output is affected:
https://gist.github.com/HeartSaVioR/04aa5ef2c17b738b2d6533394ff50723
Please let me know if any documentation works are needed.
Thanks in advance!
> Metrics Collector API: Introduce basic series aggregation functions
> -------------------------------------------------------------------
>
> Key: AMBARI-17027
> URL: https://issues.apache.org/jira/browse/AMBARI-17027
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-metrics
> Affects Versions: 2.4.0
> Reporter: Jungtaek Lim
>
> AMS doesn't provide tag so metric is identified by appId, metric name,
> hostname, instanceId. In this situation metric name is normally consist of
> origin metric name and tag values, like graphite, but unlike Graphite, AMS
> also doesn't provide series aggregation functions so aggregation should be
> done from caller side.
> It would be great if Ambari Metrics Collector provides series aggregation
> functions, like sumSeries / averageSeries / minSeries / maxSeries on Graphite.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
