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 Submitted
Created by Guest
Created on Feb 19, 2026

Extend SelfMonitoring to allow non-default-namespace Prometheus instances to scrape metric data

Customers with existing cluster monitoring solutions can't fully use the native Self Monitoring capability as the provided NetworkPolicies only permit monitoring (Prometheus) traffic from the "expected" default namespaces (openshift-monitoring / openshift-user-workload-monitoring). A customer with a defined/customised Prometheus instance in a different namespace will fail to scrape metrics from AIOps pods that already have Network Policies; adding a new NetworkPolicy can't be done globally across the AIOps namespace because pods that previously didn't have one will now fail in normal communications. Several options are possible to enable this:

1) (preferred) Tag all AIOps pods that expose metrics with a specific label so that customers can add their own NetworkPolicies to permit metric scraping by targetting that tag
2) Provide documentation on all deployed NetworkPolicies provided by AIOps to allow Customers to identify and modify to enable monitoring by non-default-namespace Prometheus instances
 

Idea priority Medium