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 Sensor
Created by Guest
Created on Jun 18, 2024

Instana agent must bring metrics from multiple database services with different ports on local host.

The current Instana implemented code picks the “port” number from configuration.yaml file and figures out that what is database service name (or SID) and connects and brings-in corresponding metrics.

 IBM developers may update the code to read multiple ports from the same “port” variable from configuration.yaml file which has some delimited (for example: comma delimitation) port numbers. Then loop through the existing reusable code which identifies the database service (SID) based on the port number for each port in the variable. All other logic in place which takes care of brining-in the metrics.

This solution will handle multiple scenarios of database services (SID) and reduce the burden on end users such as USPTO.

 

Idea priority Urgent