Bug 911652 - Redundant metrics displayed when selecting resource group metric on dashboard portlet
Summary: Redundant metrics displayed when selecting resource group metric on dashboard...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: UI
Version: JON 3.1.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ER01
: JON 3.2.0
Assignee: Jay Shaughnessy
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-15 14:34 UTC by Libor Zoubek
Modified: 2015-11-02 00:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Libor Zoubek 2013-02-15 14:34:51 UTC 
Description of problem: When I try to add a portlet that shows resource group metric list of metric contains redundant items. It happens on compatible group of CPU resources, which all has 3 metrics enabled


Version-Release number of selected component (if applicable):
JON 3.1.2.GA

How reproducible: always


Steps to Reproduce:
1. have agent with more than 1 CPU
2. create compatible group from all CPUs
3. enable same metric on all CPU resources (System Load, User Load, Wait Load)
4. go to dashboard, edit
5. add a portlet of type 'Resource Group Metric Graph'
6. select your CPUs resource group
7. pop-up Metric combo
  
Actual results: you can select 3x<CPU num> metrics, names are redundant. It is confusing.


Expected results:there should be only 3 metrics listed.


Additional info:
Comment 1 Jay Shaughnessy 2013-04-12 19:06:27 UTC 
commit 472b54ebb2885264850c4dfa796359a2cdfd9f8d
Author: Jay Shaughnessy <jshaughn>
Date:   Fri Apr 12 15:01:08 2013 -0400

Fixed
Comment 2 Larry O'Leary 2013-09-06 14:30:51 UTC 
As this is MODIFIED or ON_QA, setting milestone to ER1.
Comment 3 Libor Zoubek 2013-09-24 13:04:24 UTC 
verified on JON 3.2.ER1
Comment 4 Libor Zoubek 2013-09-24 13:04:39 UTC 
verified on JON 3.2.ER1
Note You need to log in before you can comment on or make changes to this bug.