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 Future consideration
Workspace Instana
Categories Common
Created by Guest
Created on Jan 18, 2023

On the Application Dashboard, Provide Total Wait (Latency x Calls) in the dashboards. This would definitely could be added to the top services widget.

The App Dashboard doesn't really let you know what is the busiest service or endpoint that has the most wait.   The calls let you know it's busy, but you don't know if it's a problem because it could be a really fast cached call.   The latency is good, but you don't know if it's called a lot, so it might be a waste of your time if it's got a 5 second latency but only called once.   However, if its 5 seconds and called 10,000 times an hour, total wait graph would easily show that as the top.   So if we had another options for Total Wait (calls x latency) to sort by, that would help.   What I'm looking to do is find what the applications are waiting on the most when I'm trying to make the applications faster and I think this would improve the speed of finding the problems.      

I would like to see a graph that shows the top so many calls in a area graph over time to identify problem calls.  Kind of like the Call graph in the top left, but show what calls are being made and stacked up to see what is causing the total wait.  For example, we may have a problem every 15 minutes and I want to see the spikes of total wait for all calls over time.   It is possible to do this in the analyze traces/calls, but I'm looking for something out of the box that is easy for developers that aren't proficient in using instana.  This would allow developers to open the application dashboard and easily see what is their busiest call or look at a specific time to see what causes their application to slow down based on calls without having to dig into all the traces.   These graphs would then have links to take you to the traces.   

This would also help those really big traces that don't display correctly, but you could still identify the calls that are being made in those large traces from total wait dashboards.   


Idea priority Low