Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 27 Apr 2015 17:53:40 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12824335.1430152771000.40089.1430157220450@Atlassian.JIRA>
In-Reply-To: <JIRA.12824335.1430152771000@Atlassian.JIRA>
References: <JIRA.12824335.1430152771000@Atlassian.JIRA>
 <JIRA.12824335.1430152771371@arcas>
Subject: [jira] [Commented] (AMBARI-10772) Create widget -> Add metric
 popup: Aggregator Function dropdown for component metrics
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AMBARI-10772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14514535#comment-14514535 ] 

Hadoop QA commented on AMBARI-10772:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12728453/AMBARI-10772.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/2536//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/2536//console

This message is automatically generated.

> Create widget -> Add metric popup: Aggregator Function dropdown for component metrics
> -------------------------------------------------------------------------------------
>
>                 Key: AMBARI-10772
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10772
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.1.0
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>            Priority: Critical
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-10772.patch
>
>
> When user selects any service component like All NameNodes or Datanodes (*and not a specific host component like Active namenode or Active ResourceManager*), Add metric popup should show an additional label *Aggregator Function* at the end and a corresponding bootstrap button/dropdown having following options:
> * avg
> * sum
> * min
> * max
> By default avg should be selected. Selected value from the dropdown should be shown on the  button. Hovering this dropdown should show a popover with text "This mathematical function will be applied to compute single value for selected metric across all host components".
> If user selects any option other than avg, metric path should be suffixed with ._$\{aggregator function name\}. For example if user selects a metric with name *regionserver.RegionServer.numOpenConnections*. It's corresponding metric path as known from API data obtained from metrics descriptor is *metrics/hbase/ipc/IPC/numOpenConnections*. If user then selects an aggregator function *sum*, metric path prepared for the metric element in the metric Array of the widget API definition should be saved as  *metrics/hbase/ipc/IPC/numOpenConnections._sum*. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)