This is an IBM Automation portal for Cloud Management and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - including Orchestration and Performance Management
Cloud Pak for Watson AIOps - including Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
IBM Turbonomic ARM
ITM-APM Products - including IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - including Workload Scheduler
Tivoli System Automation - including Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
Enable Multi Resource Graphing to have the option of going over 100% so that vCPU which can peak to 150% or more can provide context for rightsizing.
It used to be that the multi-resource graph went above 100% but some customers didn't like that. So it was capped at 100%.
This customer though sees big value in seeing when those peaks happen for proper context on rightsizing decisions and troubleshooting.
I see 2 possible solutions
1) Make a radio button so the user can CHOOSE Capped at 100% or Not Capped at 100%. so the graph will just go up to whatever the large value was
2) Make the data points over 100% pop either with colour or the actual value - like 150%
Do not place IBM confidential, company confidential, or personal information into any field.