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 Not under consideration
Workspace Instana
Created by Guest
Created on Mar 19, 2021

Mapping of MySQL in Application Perspective - Service Naming Rules

my idea would be to create a service mapping like this:
{
"tagFilterExpression": {
"type": "TAG_FILTER" 
"name": "call.http.host" 
"value": "" 
"operator": "EQUALS" 
"entity": "NOT_APPLICABLE"
} 
"unmonitoredServiceName": "MySQL_" 
"description": "Map MySQL database schemas to a dedicated service" 
"enabled": true
}
In this case I would assume that a service is created for each schema. However I see there two major issues with this apporach:
1) We need to create a mapping for each schema.
2) The service is not mapped to the infrastructure anymore. With this I assume that we would loose the support for automated correlations issues. E.g. lets assume there is a high load on the database server and at the same time the response time of the application goes down. Right now I would assume that Instana can correlate the events as the service is linked to the infrastructure. With the manual unmonitored service this link would not exist anymore I assume.