Skip to Main Content
Cloud Management and AIOps
Hide about this portal


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 Mar 7, 2025

Flow Rules and grouping Collectors

See this idea on ideas.ibm.com

I would like a way to have a group of flow collectors in SevOne grouped then be able to use that group inside flow rules. Thus allowing me to have a USA group, An EMEA group and so on. Now I can easily say "For all flow collectors in the DNC_Japan group only allow flows from the Routers_Japan" group" in a single rule instead of making a per-DNC flow rule. 

Idea priority Low
  • Guest
    Reply
    |
    Mar 7, 2025

    For the flow input, router, side I agree and use that function. BUT, what about on the collector side? I have at least 5 DNC servers in the US alone and quickly growing. Expand that to all global regions and I have a lot of, in my mind excess, flow rules which could be boiled down to five rules in total. I need to define a new flow rule per DNC server allowing the flow input group "USA_Routers" to the single DNC "USA_DNC07". Sure would be nice to have a single rule "<flow input group> permitted to <flow collector group>" instead of remembering to make a new rule for every DNC deployment.

  • Admin
    Matt Sweet
    Reply
    |
    Mar 7, 2025

    Hi there, just a quick FYI while we consider this. If you are polling devices via SNMP and they are getting mapped to Flow devices by their interface index in SNMP, you will be able to utilize Device Groups in reporting to achieve largely the same outcome.