Bug 1069773 (JON3-27) - Add multi-metric stacked and grouped graph support
Summary: Add multi-metric stacked and grouped graph support
Keywords:
Status: CLOSED EOL
Alias: JON3-27
Product: JBoss Operations Network
Classification: JBoss
Component: UI
Version: JON 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-25 15:57 UTC by Heiko W. Rupp
Modified: 2019-06-17 14:47 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-06-17 14:47:23 UTC
Type: Enhancement
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1069698 0 unspecified CLOSED Add Group metric graph to show multiple lines for each resource 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1070223 0 unspecified CLOSED Port metric graphs to angular 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1070352 0 unspecified CLOSED Increase the limit of resources allowed to be used in a metric group chart 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker JON3-27 0 Major New Add multi-metric stacked and grouped graph support [PRODMGT-527] 2019-06-17 14:47:21 UTC

Internal Links: 1069698 1070223 1070352

Description Heiko W. Rupp 2014-02-25 15:57:47 UTC 
Some metrics are relative to one another and it is important to be able to see these related or relative metrics within a single chart or graph. For example, when reviewing CPU usage for a CPU core or platform CPU, it is important to see the breakdown of user, nice, system, and wait load as they relate to each other.


See also JON3-26
Comment 1 Filip Brychta 2019-06-17 14:47:23 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.
Note You need to log in before you can comment on or make changes to this bug.