Key Task: Monitor 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 people use them, how often they use them, their stability (errors or crashes), and their web-based performance. This data is available by default, without requiring you to create any custom activities.

For example, you can check the adoption rate of an app, or see if apps make too many HTTP requests which can be expensive. Or you can see at a glance the number of times an app was launched or loaded from the background, the responsiveness of its internet connections, and how often it uses network connections.

Monitor Mobile Apps dashboard


  1. Step 1 Open a browser and sign in to Aternity.
  2. Step 2 Select Main Menu > Monitor > Mobile Apps.
    Access the Monitor Mobile Apps dashboard
  3. Step 3 Use the Apps section as an overview of key metrics of all monitored mobile apps, including how often people use them, their stability, and their network performance.
    View the app performance statistics

    Check the stability of each app by viewing the proportion of crashes and errors. You can also see at a glance when apps experience problems with their HTTP network communication to the server (the highest HTTP error rate, or the longest HTTP response).

    Field Description
    App Name

    Displays the name of the monitored mobile app, as it appears throughout Aternity. You can customize it if you add it as a managed application.

    App Crashes

    Displays the total number of app crashes, across all mobile devices, during the dashboard's timeframe.

    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).

    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.

    App Errors

    Displays the total number of app errors during the dashboard's timeframe.

    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.

    App Loads

    Displays the number of launches of a monitored mobile app, and the number of times a user loaded it to the foreground.

    HTTP Requests

    Aternity monitors a monitored mobile app's HTTP requests every time it sends a web request over the network. It monitors web traffic which uses the UIWebView, NSURLConnection or NSURLSession frameworks in iOS, and in Android.

    HTTP Errors

    Displays the total number of HTTP errors.

    Web errors are errors experienced by applications which receive an error as a response to their HTTP request for a page load, like HTTP 40x errors (like Error 404 Page Not Found), and 50x errors (like unauthorized access messages) for the whole page (not a missing element like an image).

    HTTP Response

    Displays the average HTTP response time during the dashboard's timeframe.

    Aternity monitors a monitored mobile app's HTTP response time as the time from the moment you sent a URL request, to the final response which arrives from the web server. It monitors web traffic which uses the UIWebView, NSURLConnection or NSURLSession frameworks in iOS, and in Android.

    HTTP Error Rate

    For monitored mobile apps, the web error rate is the percentage of web errors (HTTP error 40x or 50x) out of all HTTP requests.

    For further information, you can drill down to:

  4. Step 4 View the app's performance and usage data in each location on a geographical map to see the global distribution of HTTP usage, errors or crashes.
    Check usage in locations, and find those which suffer the most from errors or crashes

    For example, if your app has many crashes in all offices in the Far East, consider checking that your code fully supports double-byte character sets. Another example, if you find a spike of web errors in one location, check the network and firewall connections from that location.

  5. Step 5 View the app's adoption rate and stability in the top right graphs of the dashboard.

    For example, verify if employees are adopting the new version of your app by validating if the number of app loads is as expected. If the usage is low, check for poor performance (a rise on the App Crashes / Errors) graph) at that time.

    View if your app is used according to the schedule

    Hover over the graph to view the date and the exact values in the pop-up window.

    To troubleshoot an increase in errors or crashes, select a point on the graph to show data only for that time slot, then in the Apps section, drill down to the App Crashes dashboard to view the worst performing devices, crash details, or to download the crash dump file.

  6. Step 6 View the recent trend in the app's performance of HTTP requests in the Web Services section.

    If your app relies on web data intensively, this graph increasingly reflects the overall performance of your app.

    HTTP response times have a status like all other activity response times relative to their recent performance (baseline).

    Check if HTTP errors are going up or down
    Field Description
    All Requests

    View the proportion of problematic web requests out of the total, by displaying the status and volume of all web requests.

    Exclude Normal

    View only problematic web requests with a status of minor, major or critical).

    Focus on HTTP requests which were slow or had an error
    Error Rate

    View the trend in web error rates to see if recent changes improved or worsened performance. For monitored mobile apps, the web error rate is the percentage of web errors (HTTP error 40x or 50x) out of all HTTP requests.

    View the recent trend in web errors
  7. Step 7 To see an app's performance in a single location, select it in the map and check the information in the other sections.
    Isolate and view the performance of a single location

    For example, if the Munich office reports numerous errors when they use a specific feature of your company's app, select Munich on the Geographies map and view the user experience in this location.

  8. Step 8 You can jump straight to related dashboards using the tabs at the top of the screen:
    Use the quick jump bar to jump to related dashboards
  9. Step 9 You can limit the display of the dashboard using the menus at the top of the window.
    Focus on a specific app or time period, which needs your attention
    Field Description
    Timeframe You can limit the scope of this dashboard in the Timeframe field at the top of the screen. You can access data in this dashboard (retention) going back up to 30 days. This dashboard's data refreshes every five minutes.

    Displays the name of the monitored application, as it appears throughout the system. You can customize it when you add it as a managed application.

    App Version

    Displays the version of the app you selected in the App menu.