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 SevOne
Created by Guest
Created on Aug 19, 2025

"discover-netflow" should display the current source of flow in mapped instead of the last link

Given the way Netflow is design, its possible to fail over from a  lab environment was able to continue collecting netflow. However, there is a little caveat when it comes to the display name and management:

Currently the NMS does not actively track the device that is sending the flow in your active/passive configuration on these devices. The device maps seem to persist and not clean up after the direction changes from a device perspective, despite the `discover-netflow` command able to parse and listen interfaces from both.

This means that, in practice, DI would render device A in the dropdown and ultimately display B once data is graphed which can result in limited management as the policies configured might not be pointing to the relevant device/source.

Idea priority Low