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

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.

Add a new idea Subscribe
Status Not under consideration
Workspace Instana
Categories Self Hosted
Created by Guest
Created on May 12, 2026

RELATED IDEAS

stanctl install path for air-gapped and non-air-gapped need to be the same

The customer initially did their Standard Edition install using the air-gapped package.   Per the installation instructions, stanctl is placed in /usr/local/bin.   Later, the customer was able to get the Instana repos white listed and changed to online upgrades.   The problem is that when you do a yum update/yum install, it places stanctl in /usr/bin.   It doesn't update the existing stanctl that is in /usr/local/bin.

In the customer environment, /usr/local/bin was first in their path.   So, even though the customer ran a yum update, the version of stanctl didn't change.

If the air-gapped installation and the online installation used the same path (either /usr/bin or /usr/local/bin), then we could avoid this problem.  

If we choose /usr/bin, we need to notify provide instructions to existing customers to move stanctl to /usr/bin.  If we choose usr/local/bin, we will need to provide instructions for our existing online customers or move the file when we do a yum update.

Idea priority High
  • Guest
    May 21, 2026

    This is completely unreasonable. The customer wants to preserve their existing environment. They don't want to cleanup and remove things.


    This was just sloppy development. You should have a consistent experience for all of our customers. Think about product support. They need to debug problems. With customer A they will look in /usr/lib and not find stanctl. Or, they will look in /usr/local/lib.


    Having inconsistencies in the product is just plain BAD.

    Reply

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.