[
https://issues.apache.org/jira/browse/AMBARI-18125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418656#comment-15418656
]
Hadoop QA commented on AMBARI-18125:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12823374/AMBARI-18125.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8395//console
This message is automatically generated.
> AMS : Allow for certain metrics to skip aggregation determined by client
> ------------------------------------------------------------------------
>
> Key: AMBARI-18125
> URL: https://issues.apache.org/jira/browse/AMBARI-18125
> Project: Ambari
> Issue Type: Task
> Components: ambari-metrics
> Affects Versions: 2.4.0
> Reporter: Aravindan Vijayan
> Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-18125.patch
>
>
> _Example_: Per disk metrics / host static info (no aggregation across hosts)
> The client should be able to submit a request which dimension should be
> skipped.
> The metadata can store this info and allow the SELECT query projection to
> skip a chunk of these metrics based on what aggregation is working.
> For now only across host skipping makes sense and the client part can be put
> in later.
> *Note*:
> Sub-task, de-normalize disk metrics so that user can find out disk per host.
> Grafana implication: The non-aggregated metrics can obviously be visualized
> only on the templatized / host dashboard
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
