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 Functionality already exists
Workspace Instana
Categories Tracing
Created by Guest
Created on Jul 19, 2022

Enable custom Instana SDK instrumentation on an individual pod

Adding custom spans to Java applications using the Instana SDK requires configuration on the agent.

When the Instana agent is deployed as a DaemonSet in an OpenShift cluster, this configuration is centralized and is then applied to all Java applications running within the OpenShift cluster. Thus, the hot attach of the Instana javaagent requires a full search of all the packages listed in the centralized configuration file and causes the JVM to pause for an extended period of time as more packages are added to the centralized configuration. This slows pods from reaching a readiness state, has the potential to cause liveness probes to fail, and stops event-consuming applications from processing events. Ultimately, including packages in the centralized configuration is not sustainable in a production environment because of the adverse effects across all the Java applications in the cluster.

This configuration needs to be delegated to the individual pods so the entire cluster isn't impacted. The configuration parameter com.instana.plugin.javatrace should be configurable on the application pod and not just via the centralized configuration, possibly using the files functionality:

In addition, delegation of the configuration to pods/processes should be available for all of the stanzas, including JMX as well.

Idea priority High