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:
Post your ideas
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - incl Orchestration and Performance Management
Cloud Pak for Watson AIOps - incl Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - incl IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - incl Workload Scheduler
Tivoli System Automation - inc Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
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).
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
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.
Do not place IBM confidential, company confidential, or personal information into any field.