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 Instana
Categories Tracing
Created by Guest
Created on Feb 23, 2024

Need a lighter weight solution for autotrace webhook

Customers use the autotrace-webhook to avoid having to manually configure each and every deployment that they deploy into their kubernetes environment.   But, the current implementation of the autotrace webhook is pretty heavy weight and can  cause some problems in the cluster. 

When we do our deployments, the application services being deployed are quite large.    A single application service can contain up to 1200 pods.   When deploying with the autotrace webhook, additional software is added to each and every pod that is being deployed.  In the case of node.js, the additional software can be larger than the actual node.js application workloads.   with the default configuration, an additional 300 Meg of software is being deployed with each of the 1200 pods.    With some tuning and configuration changes, we have managed to reduce the size to 30 Meg.  But, that is still considerable when you consider that 1200 pods are all spinning up at the same time (30 Meg times 1200).  

With the current implementation, deployments were increasing by more than 10X the duration.  Deployments go from 5 minutes to more than 1 hour.  In addition, the deployments are causing high disk I/O for the storage.   With tuning, we have gotten the deployment times down to something manageable, but disk I/O is still quite high.  And, it required that the cluster be reconfigured with faster storage and other configuration changes.  This required downtime on the cluster.  In order to implement this across the enterprise, other kubernetes clusters would require downtime.    We are trying to avoid any maintenance that requires downtime on the production clusters.

What we would like to see is an option with the autotrace webhook where there is a global deployment of software.  And, the autotrace webhook only needs to update the nodes.js includes so that the pod can include the globally deployed software.  

If desired, we would be happy to speak with the product manager and/or engineering team to ensure that you understand the challenges and to allow us to provide feedback on any propopsed solutions.


Idea priority High