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.
With the above, I will set this idea to "Delivered".
Hi Oscar, thanks a lot for coming back on this.
I'm happy to let you know we have now an agent non-root installation on Linux in a public preview. You can find the documentation here: https://www.ibm.com/docs/en/instana-observability/1.0.315?topic=il-running-agent-as-non-root-user-linux-public-preview
Let me know if this helps and post any additional questions.
Best regards
Henning
Hi Henning,
I understand that the agent can be restarted from the Instana interface and configured via GitOps, but in this case, the client requested this feature because the agent was in an idle state; that is, it was running but not reporting to the Instana interface. The client did not have access to the root user due to internal policies, and the process to request access takes 24 hours. They needed to stop the agent to restart MQ. MQ could not be restarted because it was stuck in a synchronization state with the agent, but this synchronization could not complete because the agent was idle.
Regards
In addition to the above, we are working on remote agent config with automated roll-out. Expect news during 2026.
Best,
Henning Treu - Product Manager Instana Agent
Hi Oscar,
this seems to be about interacting as an administrator with root-owned config files, etc.
I think this can be achieved by other means:
Agent can be restarted through the Instana UI
Agent can be re-configured through gitOps feature
Permissions on Agent local files can also be changed, so that other users can interact with them.
Best,
Henning Treu - Product Manager Instana Agent