Cloud 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.

Add a new idea Subscribe
Status Planned for future release
Workspace Instana
Categories Kubernetes Tracing
Created by Guest
Created on Jul 8, 2025

RELATED IDEAS

Implement namespace exclusion functionality for new Kubernetes sensor (k8sensor)

Problem: Current IBM Instana Kubernetes sensor lacks namespace exclusion functionality, causing uncontrolled data collection and billing increases from system/excluded namespaces.

Business Impact: Organizations cannot control monitoring scope, leading to unnecessary costs and operational noise from unwanted namespace monitoring (kube-system, automation, management namespaces, etc.).

Current State: Both legacy and current K8s sensors fail to properly exclude namespaces - legacy sensor is EOL, current sensor missing this critical feature entirely.

Customer Need: Ability to exclude specific Kubernetes namespaces from Instana monitoring through configuration parameters (similar to legacy namespaceExcludes or environment variables like INSTANA_KUBERNETES_NAMESPACE_EXCLUDES).

Use Cases: Exclude system namespaces (kube-system)

Expected Behavior: When namespaces are configured for exclusion, they should not appear in Instana UI and no metrics/data should be collected from pods in those namespaces.

Request: Implement namespace exclusion functionality in current Kubernetes sensor with clear documentation and migration path from legacy configurations.

Priority: High - directly impacts customer billing and operational efficiency for Kubernetes deployments.

Idea priority High
  • Guest
    Sep 25, 2026

    Hi Surabhi,

    My customer, has requested a similar capability to allow cluster-specific filtering and whitelisting at both the namespace and node levels.

    I noticed that the requirement above focuses on namespace-level filtering, but does not mention node-level filtering. Will node-level support also be included in the design, or should that be submitted and tracked as a separate enhancement request?

    Additionally, could you please share the planned release timeline for this feature? Having that information will help us set expectations and communicate the roadmap to our customer. Thanks.

    Reply

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.