ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jungtaek Lim (JIRA)" <>
Subject [jira] [Updated] (AMBARI-17027) Metrics Collector API: Introduce basic series aggregation functions
Date Wed, 08 Jun 2016 01:22:20 GMT


Jungtaek Lim updated AMBARI-17027:
    Attachment: AMS-grafana-query-metric-wildcard-without-series-aggregation.png

Attached screenshot.

Note: Graph seems odd when we provide hostname.
It's just a limitation of current Storm metrics (measure time mismatch between tasks), and
it would be fine when we use 'minute' precision or remove hostname.

> Metrics Collector API: Introduce basic series aggregation functions
> -------------------------------------------------------------------
>                 Key: AMBARI-17027
>                 URL:
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-metrics
>    Affects Versions: 2.4.0
>            Reporter: Jungtaek Lim
>         Attachments: AMS-grafana-query-metric-wildcard-with-series-aggregation-avg-with-host.png,
AMS-grafana-query-metric-wildcard-with-series-aggregation-sum.png, AMS-grafana-query-metric-wildcard-without-series-aggregation-avg.png,
> 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

View raw message