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 Future consideration
Workspace IBM Turbonomic ARM
Categories Action Automation
Created by Guest
Created on May 12, 2023

Have a way to control how many action to send to ServiceNow

We would like to integrate our Turbonomic with ServiceNow for VM right-sizing actions.

But we found out that once we turn on that automation, Turbonomic is going to send all (1000+) of actions to ServiceNow ... that is not acceptable as it will flood our ServiceNow and the change management process required for each action.

When we were using Densify, it has a parameter that we can specify on the maximum number of resize ticket it will create on ServiceNow.  

e.g. we allow a maximum of 30 outstanding tickets, once some tickets are processed (closed/cancelled), Densify will then send more ticket to ServiceNow.

To allow that control on Turbonomic, I think we need .......

1. A way to prioritize critical actions based on utilization.  Currently, there is no way to sort all the "critical" action based on utilization data of the metric that leads to that action.  e.g. vCPU utilization for a VM that has VM up-size action  

2. Once Turbonomic can prioritize (sort) critial actions based on utilization..... we need a way to control how many TOP action we want to send to ServiceNow.


The objective is to prioritize and send the most critical (based on utilization) action to ServiceNow and not flooding the system and the change managemment process with thousands of actions.

We won't be able to adopt the Turbonomic / ServiceNow automation if we have no way to prioritize and only send a limited number of action to ServiceNow.

I know we can setup to only send action for specific group of VMs, but that is not good enough as we have to take care of all the VMs and we cannot only right-size a very small number of VMs and ignore the need for the rest of the environment.



Idea priority Urgent
  • Admin
    Simon Ravenscroft
    Jun 13, 2023

    Thanks Simon.. This is a great idea and one I recall us discussing. I've tagged it as future consideration. We periodically refresh our integrations and I will consider this as a requirement to that.

    Very interested to hear from other customers on whether this would be useful to them and what else we should do to improve our ServiceNow integration.

    BTW.. we just launched support for Utah and the ability to consolidate CRs per entity (rather than one CR per action). This may help here.