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.
Specific links you will want to bookmark for future use
The customer wants to enable metric collection for their Nginx-based application. These applications are containerized and running on OpenShift. We totally understand that we should change nginx.conf file in order to enable metrics collection (https://www.ibm.com/docs/en/instana-observability/current?topic=technologies-monitoring-nginx#distributed-tracing). However, there are lots of pods are already deployed to OpenShift and working fine. Is there an alternative way like OpenShift-wise / agent-wise parameter to enable metric collection?
.The customer Nginx servers are already deployed and running. They don't change or redeploy them often (like once in six months) and they have lots of them. So, manually changing that conf file on pods is neither an easy nor a good idea. That's why we are investigating whether there is a method to apply that setting without build&deploy.
Do not place IBM confidential, company confidential, or personal information into any field.