You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Aravindan Vijayan (JIRA)" <ji...@apache.org> on 2016/09/14 22:17:20 UTC
[jira] [Updated] (AMBARI-18125) AMS : Allow for certain metrics to
skip aggregation determined by client
[ https://issues.apache.org/jira/browse/AMBARI-18125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aravindan Vijayan updated AMBARI-18125:
---------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to branch-2.5 and trunk.
> 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)