Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Thu, 29 May 2014 17:49:03 +0000 (UTC)
From: "Oleg Nechiporenko (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12717306.1401384839010.40581.1401385743650@arcas>
In-Reply-To: <JIRA.12717306.1401384839010@arcas>
References: <JIRA.12717306.1401384839010@arcas>
Subject: [jira] [Updated] (AMBARI-5928) Create and populate Metrics section
 of a slider app
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMBARI-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oleg Nechiporenko updated AMBARI-5928:
--------------------------------------

    Attachment: AMBARI-5928.patch

> Create and populate Metrics section of a slider app
> ---------------------------------------------------
>
>                 Key: AMBARI-5928
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5928
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.6.1
>            Reporter: Oleg Nechiporenko
>            Assignee: Oleg Nechiporenko
>             Fix For: 1.6.1
>
>         Attachments: AMBARI-5928.patch
>
>
> A running slider app should show the metrics section (hidden otherwise). The metrics section should be populated by graphs which should be laid out 4 per row. 
> The way to determine the metric names for a running app is to look at the "metrics" property in response. 
> GET {{api/v1/views/SLIDER/versions/1.0.0/instances/SLIDER_1/apps/?fields=*}}
> {code}
> {
>   "href" : "http://c6401:8080/api/v1/views/SLIDER/versions/1.0.0/instances/SLIDER_1/apps/?fields=*&_=1401333569972",
>   "items" : [
>     {
>       "href" : "http://c6401:8080/api/v1/views/SLIDER/versions/1.0.0/instances/SLIDER_1/apps/1401327484490_6",
>       "appVersion" : "0.96.0.2.1.1",
>       "description" : "apache hbase is the hadoop database, a distributed, scalable, big data\n      ...",
>       "diagnostics" : "",
>       "endTime" : 0,
>       "id" : "1401327484490_6",
>       "instance_name" : "SLIDER_1",
>       "name" : "f4",
>       "startTime" : 1401332206359,
>       "state" : "RUNNING",
>       "type" : "hbase",
>       "user" : "yarn",
>       "version" : "1.0.0",
>       "view_name" : "SLIDER",
>       "yarnId" : "application_1401327484490_0006",
>       "components" : {
>       	...
>       },
>       "configs" : {
>       	...
>       },
>       "jmx" : {
>         "ClusterId" : "67ee848a-8576-45d3-9b18-cdda4eb6c025",
>         "DeadRegionServers" : "1",
>         "IsActiveMaster" : "true",
>         "MasterActiveTime" : "1401332251511",
>         "MasterStartTime" : "1401332248911",
>         "RegionServers" : "1",
>         "ServerName" : "c6401.ambari.apache.org,60000,1401332245896",
>         "ZookeeperQuorum" : "c6401.ambari.apache.org:2181",
>         "cluster_requests" : "14496",
>         "metricAverageLoad" : "2.0"
>       },
>       "urls" : {
>         "JMX" : "http://c6401.ambari.apache.org:44209/jmx",
>         "Metrics" : "http://c6401.ambari.apache.org/cgi-bin/rrd.py?c=Application1",
>         "UI" : "http://c6401.ambari.apache.org:44209/master-status"
>       },
>       "metrics": {
>       	"jvm/memNonHeapUsedM": "1024",
> 	"jvm/memHeapCommittedM": "256",
> 	...
>       }
>     }
>   ]
> }
> {code}
> Each of the key in the "metrics" property becomes a graph.
> The way to get time-series information for that graph is by calling 
> {{api/v1/views/SLIDER/versions/1.0.0/instances/SLIDER_1/apps/app1/metrics/jvm/memNonHeapUsedM}} - which should provide the same time-series data as all the other graphs in Ambari.


--
This message was sent by Atlassian JIRA
(v6.2#6252)