This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
We have a customer that is trying to monitor java. By default, Instana auto-instruments everything within the kubernetes cluster. The customer doesn't want everything instrumented because it can have an impact on the application performance.
I told them that we could add an environment variable of INSTANA_IGNORE=true to the workloads that they don't want to monitor. But, that is difficult for them to implement because they have to work with dozens of application teams that own the various applications. They would prefer if we had an opt-in approach. Perhaps one global parameter that tells Instana to NOT monitor a JVM unless a 2nd environment variable exists.
Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
That would probably work, but might be a little tricky. In order to ignore java process, you have to know the java arguments ahead of time. I think they could make it work.
https://www.ibm.com/docs/en/instana-observability/current?topic=technologies-monitoring-java-virtual-machine#excluding-jvms
We discussed that option. It won't work for them because they don't control when new application workloads are deployed. They don't want to run the risk that a java pod gets deployed and starts consuming a lot of CPU due to tracing and they have no control over it. Too many teams involved that are working within the cluster.
Hi Ben,
Customers could ignore certain processes with Agent configuration, is that difficult for them as well?