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:
Post your ideas
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
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 - incl Orchestration and Performance Management
Cloud Pak for Watson AIOps - incl Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - incl IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - incl Workload Scheduler
Tivoli System Automation - inc Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
With the cgroupv2 starting to emerge maybe is a good idea to start collecting and using the PSI metrics available in machines/containers that enabled cgroupsv2. They are valid for Servers and containers.
Looking at Load Average (existing metric) doesn't give you the full perception of what is happening in your systems. Also Load average gives you only a 1min average value which in the container world is too long. Also, you need to relate Load average with other metrics to understand if you have problems.
With PSI (Pressure Stall Information), it identifies and quantifies the disruptions caused by such resource crunches and the time impact it has on complex workloads or even entire systems.
It creates 3 different files:
Inside those files you have the pressure metrics as 10, 60, 300 sec average.
Example for CPU:
root:~# cat /proc/pressure/cpu some avg10=0.03 avg60=0.07 avg300=0.06 total=5376072182
Avg10:How long have the processes stalled for the last 10 seconds Avg60: Howlong have the processes stalled for the last 60 seconds Avg300:How long have the processes stalled for the last 300 seconds Total:How long have the processes stalled since the server booted
If a process was starved of the CPU for 5 seconds in the last 10 seconds, the Avg10 column will be 50, which means 50% of the last 10 seconds.
Do not place IBM confidential, company confidential, or personal information into any field.