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 Under review
Workspace SevOne
Created by Guest
Created on Nov 21, 2024

flow de-duplication within DI

Flow duplication is a big issue when reporting and the same flow records are sent from different flow exporters (routers that the traffic transits). It's not easy to define groups or select specific devices for reporting, particularly when there a full-mesh and other complexities such as SDWAN. As a result stats are completely skewed and exaggerated and in many cases unusable when looking at the "sum" of data. Flow de-duplication has been requested many times before and again raised as an idea by Rupert Gregory, SEV1-I-219.

This idea is a variation of this in providing the capability within DI itself. We already provide the ability to split the traffic by interface. Looking at the attached example, it is clear we have the same flow from multiple sources. The idea here is to provide an option that does this in the background and collapses / filters the data based on a number of predetermined fields that have the same value. 

Without splitting it out like this the values are all added together so we end up with 4 * whatever is shown and completely inaccurate (in this simple example).

Idea priority High
  • Admin
    Krishnan Subramanian
    Reply
    |
    Dec 10, 2024

    @Guest

    what are customer use cases/costs/processes that are impacted by not having this feature?

  • Guest
    Reply
    |
    Nov 22, 2024

    The idea here is to use key fields as defined by the view selected to filter on "uniqueness". DI dynamically creates a filter (in memory) when the report is run.

  • Admin
    Krishnan Subramanian
    Reply
    |
    Nov 21, 2024

    @Guest

    I increased the priority of the ticket.

    This feature is not a simple ask given our flow architecture.

    We do have a few workarounds like:

    1) limiting flow export from devices to avoid duplicate flow

    2) selecting resources in the DI reports to avoid duplicate flow. This could be done by selecting specific directions or interfaces.

    3) use flow policies (rules) to deny duplicate flow

    4) As you have shown, displaying the data split by interface provides a way get more accurate numbers in the reports

  • Guest
    Reply
    |
    Nov 21, 2024

    Please change this to high priority (was accidentally submitted without setting)