Key Task: Monitor Mobile Apps

You can monitor the health and performance of your monitored mobile apps, by viewing a detailed summary of their performance, adoption rates, data volumes, errors and crashes.

The system offers several dashboards relating to mobile apps:

  • With the Monitor Mobile Apps dashboard, you can view a summary of the usage and performance of all the monitored mobile apps in your organization, including where they are used, how many times they are launched, the volumes of errors or crashes, and the performance of web requests.

    Viewing a summary of the mobile apps in your organization

    All this information is gathered and displayed by default for any monitored mobile app, and does not require you to create any custom activities.

    You can jump straight to related dashboards using the quick jump menu at the top of the screen:

    Use the quick jump bar to jump to related dashboards
  • The App Usage dashboard enables you to track the adoption of the app and the diversity of environments in which your app is used, by offering an overview of the number of users of apps on unique devices, where they are located, how often they launched the app, and device statistics, like the model, operating system and its version, and mobile phone carrier.

    Viewing mobile app adoption
  • The App Errors enables you to monitor and troubleshoot all mobile app errors in your organization, including viewing a list of all errors in a given app, the relevant mobile operating systems, locations, device details (like manufacturer, model, carrier) affected device names, and view the recent past to see if there has been a rise or fall in the number of these errors.

    When a monitored mobile app running on iOS 9.x or earlier reports an error (not warning) to the system log, Aternity collects it, along with the text of the error message and its severity level. Aternity monitors all errors from your iOS app in the Apple System Log (ASL), while for Android, it checks errors reported using the android.util.Log class and monitored using the logcat tool.


    If your iOS app sends debug and error messages using the NSLog function, they appear in the Apple System Log (ASL) as a warning (not error), so by default Aternity does not capture these messages. You can configure the Aternity Mobile SDK to also collect warnings if required.

    Viewing a summary of the errors of mobile apps in your organization
  • With the Mobile App Crashes dashboard, you can view the number of crashes in each mobile app across all mobile devices, and view each set of crashes grouped by the type of exception encountered. You can also see details of the affected device names, and view the recent statistics to see if there has been a rise or fall in the number of these crashes. You can also remotely download the crash dump file from the device for further analysis.

    The Aternity Mobile SDK reports a crash if the app issues an unhandled exception, or if it receives an abort signal from the operating system (Android or iOS).

    View a summary of mobile app crashes in your organization
  • View more details to troubleshoot a specific mobile app crash or group of crashes by drilling down from the App Crashes dashboard to the Crash Details dashboard. The crash details include the last 50 instances of this type of crash, and the device model where it happened, so you can easily see if there is a correlation with device hardware.

    Viewing details of a single crash type

    For every mobile app crash, Aternity collects the exception's code and type, and the app's stack trace, a summary of the crash information, and offers you to download the dump file if needed. It also collects any breadcrumbs leading up to the crash.

    Monitored apps collect several breadcrumbs by default, including the launch time of the app, the timestamp when the app was last in the foreground, the timestamp when the app was last moved to the background, and the names of the last 20 screens shown in the app since its launch. As a mobile app developer, you can also create your own customized breadcrumbs by inserting leaveBreadcrumb() in the source code, with your custom text message to later help troubleshoot the cause of the crash.

  • The Mobile HTTP Performance dashboard monitors the performance of HTTP traffic from mobile apps in your organization. You can easily see the apps which are slowest at accessing data via the web, and determine if the problem is only with specific web services, operating systems or locations. You can also view the recent trend in the performance of mobile web access, to see if there was a recent increase in response times, and use this information to help track down the cause of the problem.

    View the performance of mobile web access
  • The Mobile HTTP Errors dashboard monitors three types of web traffic errors from mobile apps: 40x errors (like Error 404 Page Not Found), 50x errors (like unauthorized access messages) and non-HTTP errors. You can troubleshoot these errors by viewing if there was a recent increase in these errors, and to isolate the cause by seeing if the errors correlate with specific URLs, or web services, or operating systems or device types (model, manufacturer and so on).

    Troubleshoot web access errors in the Mobile HTTP Errors dashboard
  • The Mobile Data Volume dashboard helps mobility managers and other IT stakeholders quickly evaluate the incoming and outgoing data usage of mobile devices within their organization. Use this dashboard to identify problematic apps, devices, networks, trends and locations easily.

    View the incoming and outgoing data usage in your company