Bug 1002043

Summary:	No way to remove a chart from the monitoring->metrics view
Product:	[JBoss] JBoss Operations Network	Reporter:	Heiko W. Rupp <hrupp>
Component:	Monitoring -- Other, UI	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED EOL	QA Contact:	Mike Foley <mfoley>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	JON 3.2	CC:	fbrychta, hrupp, jshaughn, loleary, mfoley, mithomps
Target Milestone:	---	Keywords:	Reopened
Target Release:	JON 3.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1002040	Environment:
Last Closed:	2019-05-20 14:52:31 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1002040
Bug Blocks:

Description Heiko W. Rupp 2013-08-28 11:31:01 UTC

+++ This bug was initially created as a clone of Bug #1002040 +++

I have added a metric "Total number of commands received" to the Monitoring->Metrics view.
As I selected the wrong metric, I want to get rid of it again. This is not possible.

--- Additional comment from Heiko W. Rupp on 2013-08-28 07:28:54 EDT ---

Comment 1 Mike Thompson 2013-10-09 03:10:52 UTC

Currently, that is as designed. The portlet feature of the graphs for the new metrics page has been removed. The ability to see all the sparkline graphs because they take up very little space and be able to open one of the sparklines and see a large charge supplant the portal. Also, you can now click on a couple graphs and say 'Add to Dashboard' creating your own custom dashboard quickly and more powerfully by adding things aren't even on the monitor -> metrics page.

Comment 4 Jay Shaughnessy 2014-09-03 21:24:20 UTC

This is low priority and may need UX input, pushing.

Comment 5 Filip Brychta 2019-05-20 14:52:31 UTC

JBoss ON is coming to the end of its product life cycle. For more information regarding this transition, see https://access.redhat.com/articles/3827121.
This bug report/request is being closed. If you feel this issue should not be closed or requires further review, please create a new bug report against the latest supported JBoss ON 3.3 version.