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 (https://ideas.ibm.com).
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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - including Orchestration and Performance Management
Cloud Pak for Watson AIOps - including Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - including IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - including Workload Scheduler
Tivoli System Automation - including Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
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:
Do not place IBM confidential, company confidential, or personal information into any field.