Skip to Main Content
Cloud Management and AIOps

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 (

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 updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Planned for future release
Workspace IBM Turbonomic ARM
Categories Action Automation
Created by Guest
Created on Sep 1, 2023

More Elastic Scaling: Remove hardcoded restrictions on maximum observation period

For those customers that want to unleash Turbonomic to unlock elasticity in the cloud, we use the percentile and observation settings to help influence Turbo's decision making. However, it appears there are hardcoded limits to the minimum/maximum "Maximum Observation" period values. This limits customers' ability to customize the elasticity to their needs. And in some customer cases, Turbo does not scale up/down fast enough to meet application demands.

For DBs, the Max Observation Period hardcoded limits are:
- Min: 3 Days
- Max: 30 Days

For VMs the Max Observation Period hardcoded limits are:
- Min: 7 Days
- Max: 90 Days

For Volumes, the Max Observation Period hardcoded limits are:
- Min: 7 Days
- Max: 90 Days

When we try to use the API to change it to something less than 3 days we get this message:
- "Invalid Policy Setting: Value 1.0 for setting maxObservationPeriodDatabase less than minimum!"

When it comes to automating the scaling of Azure DBs or AWS Volumes, these actions are "non-disruptive". And using the minimum Maximum Observation Period of 3 Days, with a 99thP - it would take Turbo 43 minutes running at 100% utilization before it decides to scale something up. If we allow customers to go below our hardcoded value of 3 Days they can customize Turbo to respond even quicker to peak utilization. Let's not limit our users from being as elastic as they want in the cloud!

The ask: remove the minimum Maximum Observation Period of 3 days. Allow the customer to set a value to anything greater or equal to 0.1 days. 

We can keep the GUI as it remains today with the preset options (3, 7, 14, 30 days etc), but allow users to use the API to modify it to non-default values. 

- For reference, chart showing minutes needed before size up with different percentile/observation period combinations
Observation Period (Days)                    
Percentile    1 Day    2 Days    3 Days    7 Days    14 Days    30 Days
90%              144       288         432          1008       2015         4320
95%              72          144         216          504         1007         2160
99%              14          28            43            100          201            432

Idea priority High