iOS operating system of monitored device

iOS 9 or later.

Android operating system of monitored device

Android 4.4 or later.

For mobile devices, this displays the reporting status of the embedded monitoring functionality inside the app.

• The status of a device is Reporting if Aternity is actively receiving monitoring data from that device.

• (For monitored mobile apps only) The status of a device is Not Reporting if Aternity has not received monitoring data from this mobile device for at least 10 minutes. This could happen if the device is shut down, or the device has no network data connection, or the mobile app is running in the background or is not running at all.

• Stopped: (For mobile devices) Aternity Mobile reports a status Stopped when it does not collect performance data, but can still receive commands from the Aggregation Server.

Displays Reporting, Not Reporting, or Disconnected depending on the time elapsed since Aternity last received data from the Aternity Mobile SDK. Displays Stopped if you manually stopped the Aternity Mobile SDK from Aternity's advanced settings.

Displays the hostname of the Aternity Aggregation Server receiving monitoring data from this device.

Aternity Mobile SDK configuration.

Displays the current geographic location of the device.

Aternity reports location using the chosen method for location mapping.

Displays the number of CPU cores of the device.

The Aternity Mobile SDK queries the mobile operating system.

Displays the city of the current location of the device.

Aternity reports location using the chosen method for location mapping.

Displays the country of the current location of the device.

Aternity reports location using the chosen method for location mapping.

Displays the device ID of the mobile device which runs the monitored app.

• For monitored Android apps, the Device ID is made up of two parts: the first is the WiFi mac address, and the second is the software-based ANDROID_ID.

• For monitored iOS apps the Device ID is only unique per vendor ID. If your enterprise uses a single vendor ID to create several apps, then whenever they are on the same device, they report the same Device ID. But an app from a different vendor ID (like Citrix WorxMail) on the same device would report a different Device ID.

The Aternity Mobile SDK queries the mobile operating system.

Displays the type of device reporting performance to Aternity.

The Aternity Mobile SDK queries the mobile operating system.

(Mobile) Displays the Device Name field. You can customize the hostname of iOS or Android devices running your enterprise's app, so device names appear in the dashboards with a consistent naming policy. For example, you can dynamically assign the device name according to the enterprise username of the app.

You can manually set the device name in the Aternity Mobile SDK. If not, in iOS, the device name is from Settings > General > About > Name. In Android:

• (Since Android 8) Use the device's Bluetooth name, if modified from the default.

• (Since Android 8) Otherwise, use the account name of a mail app like Exchange. Requires end user approval and enabling GET_ACCOUNTS in the app's manifest.

• (Android 7 or earlier) Use the account email which registered the device with Google.

• Otherwise, use the device ID.

The Aternity Mobile SDK queries the mobile operating system.

(Android only) Displays whether the monitored device is currently in a phone call.

The Agent queries the operating system

Displays the IP of the WiFi connection if the device is reporting data via WiFi.

The Aternity Mobile SDK queries the mobile operating system.

Displays True when the mobile device is using roaming service.

The Aternity Mobile SDK queries the mobile operating system.

Displays the date and time of the last boot of the device.

The Aternity Mobile SDK queries the mobile operating system.

Displays the current geographic location of the device.

A business location refers to a site (an office building, campus, or even a part of a building) in your organization which contains monitored devices. Each location has a city, state, country, and (optionally) region, and has specific geographic coordinates to display it on a map.

For virtual applications (like Citrix XenApp), Aternity always tries to report the location of the end user's front-end device by detecting its subnet.

Aternity reports location using the chosen method for location mapping.

Displays the level of detail of the performance data which Aternity captures about the monitored application or device.

Displays only if you configured it in the Aternity advanced settings.

Displays the name of the vendor which created this device, like Samsung, Apple, and so on.

The Aternity Mobile SDK queries the mobile operating system.

Displays the size of physical RAM of the device..

The Aternity Mobile SDK queries the mobile operating system.

Displays the name of the cellular carrier to which the device is connected.

The Aternity Mobile SDK queries the mobile operating system.

Displays the name and the model number of the device, like iPhone 6s, GalaxyTab8.

The Aternity Mobile SDK queries the mobile operating system.

Displays the type of network connection of the device: Mobile or WiFi.

The Aternity Mobile SDK queries the mobile operating system.

Displays the generic name and version of the operating system (like MS Windows 10, MS Windows Server 2008 R2, MacOS 10.3, iOS 10 or Android 6)..

The Aternity Mobile SDK queries the mobile operating system.

Displays the broad category of the operating system. Use this to differentiate between different major operating system groups. For example, it displays all releases of Microsoft Windows as MS Windows, all releases of Windows Server as MS Windows Server or all releases of iOS as iOS.

The Aternity Mobile SDK queries the mobile operating system.

You can optionally define a region in Aternity to group together several locations under a single label, like the geographical region of EMEA, North America or even Southern Europe, South-Western US any other grouping you choose.

Aternity reports location using the chosen method for location mapping.

(For mobile devices) Displays the name of the site where the device is currently connected. You can set the site name for a mobile app in the Aternity Mobile SDK.

Mobile apps can set this manually in the Aternity Mobile SDK.

(Android only) Displays the name assigned to the device's storage.

The Aternity Mobile SDK queries the mobile operating system.

Displays the device's subnet configuration used to connect to Aternity (including IP v6 if the device runs Agent 10 or later).

The Aternity Mobile SDK queries the mobile operating system.

(Macs and Mobile) View the percentage battery charge for this device at any time.

Additional data related to battery status:

• Battery Charging is true or false depending on whether it is currently being charged.

• Battery Health status as reported by the operating system (not available in iOS).

The Aternity Mobile SDK queries the mobile operating system.

Displays the percentage CPU utilization of the core with the greatest usage at a given time. For example, if the device has four CPU cores, where one is at 80%, one is at 60% and the others are idle, it will display a value of 80%.

Collection of this data is not supported by Android 8 and later.

The Aternity Mobile SDK queries the mobile operating system.

Displays the amount or percentage of free space on the mobile device's storage..

The Aternity Mobile SDK queries the mobile operating system.

Displays the percentage usage of the device's physical RAM memory at a given time.

The Aternity Mobile SDK queries the mobile operating system.

(Mobile only) For mobile network connections (3G / 4G / LTE), view the signal strength to the mobile carrier, the type of phone network (like CDMA or GSM) and the name of the carrier.

(Android only) Displays the processes occupying the highest CPU percentage on the device during the timeframe, and view the maximum usage for each process. For example, when an intensive graphics application uses a high CPU for several minutes, or an application hangs.

Collection of this data is not supported by Android 8 and later.

(Android) The Aternity Mobile SDK queries the mobile operating system.

(Android only) Displays the processes which utilize the most physical memory (known as the total working set) during the timeframe, and view the maximum physical memory usage for each process.

(Android) The Aternity Mobile SDK queries the mobile operating system.

Displays the name of the company as determined by the app developer who manually set this field in the app's monitoring as part of the Aternity Mobile SDK.

Mobile apps can set this manually in the Aternity Mobile SDK.

Displays the name of the department to which the user or the device belongs.

Displays only if you configured it in the Aternity advanced settings..

Displays the job title of the current user logged in to this device. In Windows, this is the same as the AD Title.

Displays only if you configured it in the Aternity advanced settings..

Displays the username signed in to the device's operating system.

Mobile apps can set this manually in the Aternity Mobile SDK.

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

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.

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.

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.

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.

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

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.

The User Experience Index (UXI) is a value (0-5) which measures the overall performance and health of applications, based on the number of crashes per hour out of the total usage time, the percentage hang time out of the total usage time, and 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.

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

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

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.

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

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.

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.

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

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

The activity score is a value (0-100) which summarizes the statuses of all activity response times into a single value. Each value is calculated using our Apdex-inspired formula or manually set thresholds, and also has a status and color.

The status of an activity is based on one response time compared to the recent expected response time (baselined or manually predefined). The statuses are measured in severity: Normal , Minor , Major or Critical .

The SLA status of an activity determines if the response time complies with the SLA requirement (colored green ), or if it crossed the internal SLA threshold showing you risk breaking the SLA (colored yellow ), or if it crosses the external SLA threshold showing you have broken your SLA (colored red ).