Skip to Main Content
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.

Status Future consideration
Workspace Instana
Categories Extend Capabilities
Created by Guest
Created on Apr 25, 2024

Basic filtering in /api/infrastructure-monitoring/topology

Currently we're using /api/infrastructure-monitoring/topology to retrieve the list of a subset of the infrastructure snapshots and their relations. The problem is that this endpoints returns everything, and therefore produces massive responses from which we drop most of the data.

In our case, we'd greatly benefit from having a plugins query parameter that contains a list of plugins and that would have the following effect:

  • filter the list of nodes to only include snapshots which plugin is in the list of requested plugins

  • filter the list of edges to only include edges between snapshots that are included in nodes

For example, assuming that the unfiltered response would have been

GET /api/infrastructure-monitoring/topology
{
"nodes": [
{
"id": "D",
"plugin": "kubernetesDeployment",
...
},
{
"id": "N",
"plugin": "kubernetesNamespace",
...
},
{
"id": "C",
"plugin": "kubernetesCluster",
...
}
],
"edges": [
{
"source": "D",
"destination": "N",
"relation": "in"
},
{
"source": "D",
"destination": "C",
"relation": "of"
},
{
"source": "N",
"destination": "C",
"relation": "of"
}
]
}

A filtered response would have looked like

GET /api/infrastructure-monitoring/topology?plugins=kubernetesDeployment,kubernetesNamespace
{
"nodes": [
{
"id": "D",
"plugin": "kubernetesDeployment",
...
},
{
"id": "N",
"plugin": "kubernetesNamespace",
...
}
],
"edges": [
{
"source": "D",
"destination": "N",
"relation": "in"
}
]
}
Idea priority High