Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Planned for future release
Workspace Instana
Categories Sensor
Created by Guest
Created on Sep 4, 2023

Need a "Hostname" field when using a Remote monitoring sensor

With many of the Instana sensors that do Remote Monitoring (MQ, MQ FTE, DB2, Oracle, etc.), there isn't a field that allows a customer to identify the hostname of the remotely monitored system.  I'm working with a customer that it integrating Instana with Big Panda and ServiceNow and those tools require a unique hostname field.    With Instana, the hostname, is the hostname of the Agent which isn't correct.   

The customer is looking for a field that could be use with global custom payloads where they could map a field that includes the hostname of the monitored server to a specific global custom payload field.

When doing remote monitoring, we should ALWAYS include a  field such as "RemoteHost" or "RemoteHostname" that would include the fully qualified hostname of the remotely monitored system.

Idea priority Urgent
  • Guest
    Sep 5, 2023

    When remote monitoring, the Monitored_Host can be added for each technology, but need one sensor one tag, because one tag can only be implemented to one metric from code level.

    From sensor, it is not possible for a unified monitored host for different sensors by remote monitoring, as the hostname is exacted from each Sensor payload. You ask if team infra from infrastructure level to see if they have workaround for remote monitoring way.