IBM Data and AI Ideas Portal for Customers

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:

Post your ideas

Post 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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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 product management 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 notification 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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Future consideration
Created by Guest
Created on Mar 19, 2021

Increase Numeric Precision of Values used in Anomaly Detection

As explained in Support Case TS004193711, in many cases when exceptions and/or Alerts are triggered for CPU anomaly exceptions, the CPU Factor is displayed as "N/A". Also the "RollAv CPU", "ECPU RollLm" and ACPU Rollm" columns are all always zero. It is expected that all of these columns be > 0.

After sending our raw data to Support, according to QM Development, they saw that not all "ECPU RollLm" are zero, and they are definitely not zeros for P(DB2 CPU Time anomaly detected) exceptions.

'ECPU RollLm' = ('STDDEV CPU' * 'Toleration Level for Exceptions' + 'ROLLAV CPU')

'ACPU RollLm' = ('STDDEV CPU' * 'Toleration Level for Alerts' + 'ROLLAV CPU')

The 'P' exception fires when 'DB2 CPU Time' becomes larger than 'ECPU RollLm' or 'ACPU RollLm' correspondingly.

2) According to design: CQM displays only 6 digits after dot, but often values may be smaller.

That is why you see so many zeros in "RollAv CPU", "ECPU RollLm" and ACPU Rollm".

3) 'STDDEV CPU' is used as divisor when calculating of CPU Factor.

The main reason of N/A factors is that CQM uses 1e-06 precision for CPU and Elapsed display, so calculating factor for STDDEV<1.e-06 is not really practical, because initial values have this precision. So, CQM shows N/A for cases where factor may have too large a statistical error.

Needed by Date Mar 19, 2022