Mobile Applications Monitoring

by Mahalya R | October 9, 2023

How Can We Help?

Last Updated On
Print

Introduction

The HEAL Mobile Application Monitoring tool helps you track and analyze the performance of your Android and iOS mobile applications. It provides a comprehensive overview of transactions, device-wise breakups, and performance metrics.

Dashboard Overview

The dashboard is divided into several sections to give you a detailed analysis of your mobile application’s performance.

Transaction Breakup

The dashboard is organized into several key performance indicators:

  • Total: Represents the aggregate count of all transactions within the monitoring scope.
  • Success: Shows the total number of transactions that were completed successfully without any errors. This is a key indicator of the application’s reliability.
  • Failure: Tracks the count and percentage of transactions that did not complete as expected and may require further analysis to identify the underlying issues.
  • Slow: Highlights the transactions that have exceeded a predefined threshold for completion time, potentially impacting user experience.
  • Count Vs Avg Response Time (Android)” and “Count Vs Avg Response Time (iOS): These graphs compare the number of transactions (Count) over time against the average response time (Avg Response Time) for each respective service.

 

Below the Transaction Breakup, you can see the three donut charts that break down the top 5 transactions based on success, failure, and slowness metrics:

  • Transaction Breakup – Top 5 (Success): This chart shows the top 5 successful transactions, with the percentage indicating how much each transaction contributes to the success metric. Each segment is labeled with an average response time in seconds and corresponds to a specific URL or service call.
  • Transaction Breakup – Top 5 (Failed): This chart represents the top 5 failed transactions. Similar to the success chart, each slice shows the failure rate for a given URL or service endpoint. The percentage signifies the proportion of total failures, and the labels provide context for each type of failure.
  • Transaction Breakup – Top 5 (Slow): This donut chart details the top 5 slowest transactions. It highlights which transactions are taking the most time, with the percentage showing their relative contribution to the overall slowness metric. The URLs or services are labeled with their average response times in seconds.

Service-wise Transaction Stats

The “Service-wise Transaction Stats” section provides a detailed breakdown of transaction statistics for each service URL.

 

  • URL: Lists the endpoints or URLs being monitored. They typically represent different functionalities or services offered by a web application, like registration, authorization, or investments.
  • Total: Shows the total number of transactions made to each URL.
  • Success: This column indicates the number of successful transactions for each URL.
  • Success%: Represents the percentage of successful transactions relative to the total number of transactions for each URL. It’s a key indicator of how reliably each endpoint is performing.
  • Failed: Displays the count of failed transactions per URL.
  • Failed%: Details the failure rate as a percentage for each URL. A ‘NaN’ (Not a Number) value may suggest that there was no record of failures for those URLs, or the failure rate is non-applicable in this context.
  • Slow: Lists the number of transactions that were slower than the expected threshold for each URL.
  • Slow%: Depicts the percentage of slow transactions against the total transactions per URL. It helps in identifying performance bottlenecks.

Application Traces

The “HTTP Requests Overview” section provides a detailed breakdown of individual HTTP requests that were either successful, failed, or slow. This section is crucial for diagnosing specific issues in your mobile application.

 

  • Trace ID: A unique identifier for each transaction trace.
  • Time: The timestamp when the trace was recorded.
  • URL: The specific endpoint of the web service that was called.
  • Status Code: The HTTP status code returned by the transaction. A ‘200’ code usually means success, while other codes like ‘404’, ‘500’, etc., represent various errors.
  • Response Time: The time taken for the transaction to complete, usually measured in milliseconds or seconds.

 

Table of Contents