Monitor Additional Mobile App Details

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

The system collects a comprehensive list of attributes about the mobile app and its device, and presents the data in several dashboards relating to mobile apps. Besides the Mobile Apps Summary dashboard, Aternity also offers the following mobile dashboards:

  • Use the Analyze Mobile App Errors (Advanced) dashboard to analyze 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.

    Aternity collects all errors reported from monitored mobile apps running on iOS 9.x or earlier using NSLog function. Those errors are included in the Apple System Log (ASL), and Aternity collects them, along with the text of error messages and their severity level.

    For Android monitored apps, Aternity collects all errors reported using the android.util.Log class that can be extracted using the logcat tool.

    Analyze Mobile App Errors
  • View more details to troubleshoot a specific mobile app crash or group of crashes by drilling down from the Device Health dashboard to the Crash Details dashboard. To drill-down, open Device Health, select a mobile OS and then hover over the required sub-component and click the Crash Details link. 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 code and type of exception, the app's stack trace, and a summary of the crash information. It also collects any breadcrumbs leading up to the crash. You can download the memory dump file if needed.

    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.

  • Use the Analyze Mobile HTTP (Advanced) dashboard to analyze 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 build the 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.

    Also use this dashboard to analyze 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).
    View the performance of mobile web access and troubleshoot web access errors in the Mobile HTTP Errors dashboard
  • Use the Analyze Mobile Traffic Network (Advanced) dashboard to analyze the incoming and outgoing data usage of mobile devices within organization. Use this dashboard to identify problematic apps, devices, networks, trends and locations.
    View the incoming and outgoing data usage in your company
  • Use the Business Activities dashboard to analyze the Mobile App Usage. You can 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
  • View Mobile App Crashes in the Device Health dashboard. You can view the number of crashes in each mobile app across all mobile devices. 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.

    Aternity reports a crashing monitored mobile app if it experiences an unhandled exception, or if the operating system (iOS or Android) tells it to abruptly stop (abort signal).

    View a summary of mobile app crashes in your organization