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 (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 Future consideration
Workspace Instana
Created by Guest
Created on May 12, 2022

Mobile Monitoring: Filter out network errors by default so mean latency is correct

Background and context

The mean latency information in mobile monitoring is currently very skewed by that some calls show extremely high latencies. This is due to that Instana measures some corner cases that is not really interesting from performance point of view (but might be for other purposes).

These are

  • Various network communication errors such as timeouts causing Instana to not be able to capture a correct HTTP response. These are reported with status code '-1' and often have huge latenices along with them in the range of hours or even days.

  • Cases where the user closes the app or change to another app before the mobile application has finished communication with the backend. These traces are mapped to the view 'Background' by the Instana SDK and also this category contains calls with very high latencies, often several minutes and/or hours.

From performance tracking point of view it is not interesting to include these erroneous cases for which we as app developers anyway don't have any control over. We're only interested in measuring performance of successful communication between the frontend and the backend.

Current workaround in analytics and custom dashboards

A workaround we use currently is to filter out these two categories by the Instana filters

  • HTTP Status code != -1

  • View != Background

Proposed solution

A possible way for Instana to handle this in a way so that mean latency is correct by default when viewing a set of calls from mobile monitoring is to make it configurable whether these two categories should be a part of the monitored dataset, perhaps in a similar way as in the backend monitoring where it's configurable whether to show synthetics calls or not, where the default is that these calls are excluded from the dataset.

Example:

[x] Show network errors and timeouts

[x] Show calls from Background view

Idea priority Low