Skip to Main Content
Cloud Management and AIOps


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

Status Functionality already exists
Workspace Instana
Created by Guest
Created on Feb 1, 2023

New Agent Key in case of leak or security concerns

As customer I want to ensure that when the Agent Key leaks, nobody can abuse the Key and do harmful things with it.

To be able to manage (add, manage, delete) the Keys (Sub-Keys) inside the Instana UI would help to monitor and govern who has access to which keys or limit them. Also to limit the visibility and usage of keys to specific teams or parts of the organisation.

Idea priority High
  • Guest
    Reply
    |
    Apr 3, 2023

    You are right. In an enterprise with lots of different teams wanting to deploy agent, it might be helpful to be able to create a Sub Key with limited amount of agent (or the number of agent the department bought) to govern their usage and prevent the team to no overutillize the number of licenses. And it will also give the ability to see which team uses how many licenses.

  • Admin
    Máté Návay
    Reply
    |
    Apr 3, 2023

    Access to AgentKey visibility is controlled by permissions. So far we've not found a usecase with customers where it would make sense to only access/manage part of the agent keys, as in most cases the user assigned with the permission has management rights over the infrastructure (ie can install the agent).

    The Agent Keys can be seen and managed in the UI and a need for additional capabilities have not been recorded so far.