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 Instana
Categories Extend Capabilities
Created by Guest
Created on Jun 2, 2025

Allow Zone Definition for Hosts through OTel Collector in Instana

When using the OpenTelemetry (OTel) collector to send metrics to the Instana Backend, there is currently no mechanism to define or pass the "zone" attribute for the monitored hosts. This results in all hosts being categorized as "undefined zone" within Instana, regardless of their actual geographical or logical deployment location.

This limitation significantly impacts our ability to:

  • Effectively classify metrics: Without zone information, it's challenging to group and analyze metrics based on logical environments (e.g., production, staging, development) or physical locations (e.g., Europe-West-1, US-East-2).
  • Manage large-scale monitoring: In environments with hundreds or thousands of monitored hosts, the "undefined zone" status makes it extremely difficult to navigate, filter, and troubleshoot specific host issues, leading to operational inefficiencies.
  • Leverage Instana's full potential: The lack of zone information prevents us from fully utilizing Instana's capabilities for segmented dashboards, alerts, and dependency maps, which rely on proper logical grouping of entities.

We request the inclusion of a feature that allows users to explicitly define the zone for hosts when sending metrics via the OTel collector to Instana. This could be achieved through:

  • A configuration option in the OTel collector that maps to an Instana zone.
  • The ability to pass a custom attribute or tag in the OTel data that Instana can interpret as a zone.
Idea priority Medium
  • Admin
    Paras Kampasi
    Jul 1, 2025

    Hi Jean,

    Thanks for reaching out.
    Can you please confirm how you are transporting data from the collector to Instana? Is it directly to Instana backend or is it being sent to an Instana agent first?

    Kind regards,
    Paras Kampasi