View Applications Data Collected by Aternity

Aternity monitors the performance of all applications which are automatically discovered. These include managed applications which have their own defined activities. There are additional measurements reported on managed applications only:

Monitor Performance and Usage of All Applications

For usage and performance, Aternity monitors performance like usage time, wait time and hang time for all types of apps:

  • Aternity monitors all Windows desktop applications,

  • It also monitors iOS or Android mobile apps which have Aternity functionality embedded in them.

  • While Aternity monitors all web applications which run on monitored devices, it only lists the site names if they are business-related (on our white list). It also lists the managed web applications, and any internal (intranet) web sites whose web servers are inside the enterprise network (or VPN). Aternity does NOT expose all visited websites, as this contravenes our privacy commitments. Any web pages which are not on the white list appear under the generic title Web browsing to preserve employees' privacy. To view a web site's performance in the dashboards, add it as a managed application.

    The default white listed business web applications are (in alphabetical order): ADP, Aetna, AirWatch, analytics.google.com (Google Analytics), AppDynamics, AppFirst, AppSense, Ariba, Aternity, athenahealth, Autodesk, Balsamiq, Bazaarvoice, Benefit Resource, bluecross, Box, BRiWeb, Certify, Citrix, Clarizen, Concur, Concur Solutions, console.aws.amazon.com (Amazon AWS Console), Constant Contact, Cornerstone OnDemand, Dealertrack, Demandware, docs.google.com (Google Docs), DocuSign, EchoSign (Adobe Sign), eClinicalWorks, Eloqua, FedEx, Fleetmatics, GitHub, GoDaddy, GoToMeeting, Host Analytics, iMedidata, Informatica, Intralinks, jiveon.com (CIsco Jive), Kronos, LeadGnome, LinkedIn, LivePerson, LogMeIn, MaaS360, Marketo, Microsoft, MindTouch, NetSuite, Office365, Okta, onedrive.live.com (Microsoft OneDrive), OneLogin, OpenAir, Paychex, photoshop.com (Adobe Photoshop Online), Ping Identity, Pinpointe, Proofpoint, Qlik, rainkingonline.com (RainKing), Rally, SalesForce, SAS, ServiceNow, ShareFile, SharePoint, SmartBear, Softrak, Splunk, spotfire.com (TIBCO Spotfire), successfactors.com (SAP SuccessFactors), SugarCRM, Tableau, Trello, UPS, WebEx, Workday, Yammer, Zendesk.

It also monitors HTTP performance on mobile apps and the load time of a web page on web apps.

Field Description
App Loads

(For monitored mobile apps only) Displays both the number of launches of a monitored mobile app, and the number of times a user loaded it to the foreground.

Application Name

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.

Data Volume (For monitored mobile apps only) Aternity monitors the size of a monitored app's incoming and outgoing data, and the amount of data transfer per hour. It monitors web traffic which uses the UIWebView, NSURLConnection or NSURLSession frameworks in iOS, and java.net.HttpURLConnection in Android.
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 Requests

(For monitored mobile apps only) 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 java.net.HttpURLConnection in Android.

HTTP Response

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 java.net.HttpURLConnection in Android.

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. If a user double-clicks a document which also launches the app, the launch time would include BOTH opening the application AND the time to open the document, which may be significant if the document is on a slow network or it is a large or complex file.

(Web) Page Load Time

(For web applications only) The web page load time is 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, such as iframes that are embedded separate web pages, AJAX calls after the page is complete, or bookmarks with # in the URL). It does include AJAX calls that the page makes before it is complete.

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.

Definition 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 out of the total usage time, the percentage of hang time out of the total usage time, the percentage wait time out of 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

The wait time of a Windows application 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 (Windows devices). 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

Enhanced Monitoring with Managed Applications

In addition to the above measurements, Aternity enhances monitoring of managed applications (even without any activities) by monitoring its PRC:

Field Description
IP Address

(For web applications only) Displays the IP address of a managed web application.

Process CPU of an application

Displays the average and maximum CPU usage (in percent) of this managed application over a one-hour period, which is part of the application's process resource consumption (PRC).

Physical Memory of an application

Displays the average and maximum usage of a managed application's physical memory (known as the total working set) in gigabytes over a one-hour period, which is part of the PRC.

High usage of an application's working set memory increases the chances of switching parts of the application into virtual memory, leading to an overall slowdown in performance.

Virtual Memory of an application

Displays the peak and average usage of a managed application's reserved memory (commit size) in gigabytes during a one-hour slot, which is part of the application's process resource consumption (PRC).

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

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.

Crash (on Windows, Mac) or App Crashes (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.

(Macs) Aternity registers an application crash on Mac applications if the crash is entered in the system log.

(For 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) Agent queries Windows Event Log

(Mac) The Aternity Agent for Mac queries the macOS system log.

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

Crash (After Hang)

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

(Mac) Aternity uses the system log to determine 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.

(Windows) Agent queries Windows Event Log

(Mac) The Aternity Agent for Mac queries the macOS system log.

Crash (DotNet)

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

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.

Agent queries Windows Event Log

HTTP Error Rate

(For monitored mobile apps only) The web page error rate is the percentage of errors out of all web page loads which cause the page not to load (HTTP error 40x or 50x).

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

HTTP Errors / Web 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).

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

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.