Cloud Management and AIOps
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).
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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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.
The related Aha! idea for selecting based on technology and process properties is here: https://automation-management.ideas.ibm.com/ideas/INSTANA-I-4512
Hi Martin, thanks for the prompt reply!
I acknowledge your requirement to monitor based on technologies. I'm open to discuss how we can extend Selective Monitoring, to also allow technology-based filtering of what gets monitored.
Disabling sensors via
configureation.yamlmay work, but is not meant to be the solution here. Disabling individual sensors is a way to debug certain situations, but not meant to be the control for opt-in / opt-out. The required list of sensors is sensitive and critical to the correct function of the agent.If you agree, I will open a new Aha! idea for extension of Selective Monitoring by technology (and other process properties, like process name, arguments and arbitrary environment variables).
Best
Henning
Selective monitoring is not the same as disabling unwanted sensors.
Selective monitoring requires changing the processes to use an opt in env variable - meaning everything we want to monitor needs to have it's startup edited to add the variable and then restarted.
This means we need to edit and restart literally thousands of processes across the enterprise.
We have had to implement a scripted solution to produce a configuration.yaml file with all irrelevant sensors disabled - and only certain sensors enabled. This achieves the goal without us having to restart anything but the instana agent itself.
It would be sensible for instana to have this feature natively.
This is available with "Instana Selective Monitoring" on a process level. Opt-in and opt-out mode is supported.
Documentation is life here: https://www.ibm.com/docs/en/instana-observability/1.0.313?topic=agents-instana-selective-monitoring