View Data Collected by Aternity for All Applications

Aternity monitors the performance of all applications which are automatically discovered. These include managed applications which have their own defined activities.

Monitor Health Events in All Applications

By default, Aternity monitors the health of any application by collecting application crashes (for desktop, web or mobile apps). For the health of web applications, it monitors whether the browser returns a web error:

Field Description Source
Application Crash (on Windows) or Crash Occurred (on mobile)

(Windows) Aternity registers an application crash with Windows Event Log ID 1000 (a process or DLL ends unexpectedly), event ID 1001 (.NET process ends unexpectedly), event ID 1002 (a user stops a Not Responding process), or event ID 1026 (.NET runtime error).

To resolve, note any error numbers, or check the logs of the application, then consult the support site of the application vendor.

(Monitored mobile apps only) 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).

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.

(Windows) The Agent queries Windows Event Log

(Mobile) The Aternity Mobile SDK receives a notification that the monitored app crashed.

Application Closed After Hang

(Windows only) Windows event ID 1002 occurs when a user has manually forced an application's process to close after it stopped responding.

To resolve, note any common actions leading to the hang, then consult the support site of the application vendor.

The Agent queries Windows Event Log

DotNet Process Crash

(Windows only) Windows event ID 1001 occurs when a .Net process or DLL ended unexpectedly.

To resolve, note any error numbers, or check the logs of the application, then consult the support site of the application vendor.

The Agent queries Windows Event Log

DotNet Runtime Error

(Windows only) Windows event ID 1026 appears when a handled exception in .Net occurs.

You don't have to resolve. You may check the logs of the application to see which exception occurred.

The Agent queries Windows Event Log

Error Occurred

(Monitored mobile apps only) 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.

Note

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.

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.

Web Errors

(Web applications only) Web errors are errors experienced by applications which receive an error as a response to their HTTP request, like HTTP 40x errors (like Error 404 Page Not Found), and 50x errors (like unauthorized access messages).

(Monitored mobile apps only) The Aternity Mobile SDK reports the HTTP errors and low-level TCP errors when a monitored app uses HTTP traffic.

(Windows) The Agent monitors web browsers to monitor the performance and errors in web applications.

(Mobile) The Aternity Mobile SDK monitors the app's HTTP network traffic.

By default, Aternity monitors the resource usage of popular web browsers (Mozilla Firefox, Internet Explorer v9, 10, 11 and Google Chrome) to monitor web apps which run inside them.

Monitor Performance and Usage of All Applications

For usage and performance, Aternity monitors:

  • Windows: usage time, wait time and hang time

  • Mobile: HTTP performance

  • Web: Load time of a web page

Field Description
Hang Time

Hang time measures the time when an application is listed as Not responding in the Windows Task Manager while it is in the foreground (in use). This measurement is used to calculate the wait time of an application, and the overall UXI.

HTTP Performance (mobile only)

For each HTTP request from a monitored mobile app, Aternity monitors the response time, the volume of traffic (send/receive), and in some frameworks, the time until the first HTTP response from the server.

Launch Time

An application's launch time, which Aternity measures automatically for all Windows applications and monitored mobile apps, starts when the process begins, and ends when it is ready to receive user input. In Windows, this is also when it finishes creating a window with a title bar.

Page Load Time

The web page load time is defined as the time required for a web page to load and finish rendering in a browser, from sending a URL request to when the page's events finish loading and it has a status of Completed. This measurement does NOT include the time to load additional page elements which occur after the main page has loaded (like Ajax calls which are measured separately, or iframes which are embedded separate web pages, or bookmarks with # in the URL).

Usage Time

The usage time of an application is the total time it is running, in the foreground, and being used. This includes the wait time, the time a user spends waiting for the application to respond. For web applications, the usage time is when both the browser window and the application's tab are in the foreground.

Deinition of Usage Time
User Experience Index (UXI)

The User Experience Index (UXI) is a value (0-5) which measures the overall performance and health of an application, based on several inputs: the number of crashes per hour of out the total usage time, the percentage of hang time of out the total usage time, the percentage wait time of out the total usage time. For web applications, it also uses the percentage of web page errors out of all page loads, and the average page load time. These ingredients come together to represent the overall experience of a user.

For each element of the UXI, we determine a narrow range of meaningful results, beyond which it is flattened to either zero or the maximum. For example, a regular application should have 0% hang time, so anything above 5% would be unacceptable, therefore the hang time index would be zero, which drastically lowers the overall UXI score for that application.

Definition of UXI
Wait Time

An application's wait time is defined as the time users spend waiting for the application to respond when it is actively running and in use (part of the usage time).

The total wait time is calculated as the time covered by the following components (which may overlap): the hang time when an application is not responding, or when the mouse pointer has a busy icon. For web applications, the wait time is the web page load time when both the browser window and its tab are in the foreground.

Definition of Wait Time