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.
Hi Farhad,
the logging feature (as well as the new synthetic monitoring feature) will not make it to docker-based installations, because of resource constraints of docker-based installations.
You will need to switch to an Instana Kubernetes Operator backend as you correctly linked.
Best
And I just realised the source of confusion maybe. Apologies, as the original Idea mentions Helm deployment, which is incorrect. it is a multi-host Docker Backend
Hi Hubert,
In this case, it is a multi-host Docker installation.
My understanding is that the logging feature uses a separate CH Schema which currently only gets set up when instana is deployed via the operator. So on a multi-host Docker installation (or any other on-prem installation that is not operator based), if I enable collection of docker logs in the agent, the agent will collect, but backend will not process them as the pipeline for it does not exist.
Hope this makes sense.
Hi Farhad,
can you provide more context on how the customer is setting up the backend? Which helm chart or deployment are you referring too?
Just to clarify, the customer is using the Instana Kubernetes Operator?