Software System Requirements for Devices (Agents)

This section details the minimum software system requirements for monitored devices and devices accessing Aternity.

Access Aternity Dashboards and Settings

Sign in to SteelCentral Aternity™ at https://my.aternity.com, https://us2.aternity.com, https://eu.aternity.com, or https://us3.aternity.com in a Windows browser on a monitor with resolution 1280 x 768 or more. You can view Aternity in:

  • Google Chrome version 42 and above.

  • Microsoft Internet Explorer version 11 and 11 Enterprise Mode, with Compatibility Mode disabled and third-party browser extensions enabled.

Windows Devices (Running Windows Agent)

Each monitored Windows device must have the following minimum system requirements to install the Agent for End User Devices locally:

Attribute Requirement

Windows operating system

Device must have:

  • For servers: Windows Server 2016 64-bit, Windows Server 2012 R2 64-bit, or Windows Server 2008 R2 64-bit.

  • Microsoft Windows 10, 8.1, or Windows 7 SP1 (with KB3125574) Enterprise / Professional 32-bit and 64-bit (32-bit requires Agent 9.0.6 or later).

Monitored web applications

Agent 11.x can monitor a web (cloud) application running in any of the following Windows browsers:

  • Monitor any web application in any version of Google Chrome released in the past two years. For legacy Agents (on Windows until Agent 9.1.x or on Mac until Agent for Mac 2.3), you must also manually add the Aternity Extension for Chrome to monitor web page load events (WPM) and usage. Without this, Aternity only monitors clicking a link, back, forward, direct URL, HTTP GET and POST events.

  • Monitor any web application in Microsoft Internet Explorer v9, 10 or 11. For legacy until Agent 9.2.3, monitor discovered web apps by disabling IE's compatibility mode (learn more).

  • Monitor only managed applications with custom activities or page load activities (WPM) in Firefox (beta) single process mode versions 38 ESR, 45 ESR or 52 ESR. Contact Customer Services if you have versions 45 ESR or 52 ESR to enable monitoring of custom activities, and to ensure they are compatible with your Firefox.

Connectivity

The Agent sends monitoring data to Aternity (including IP v6 for Agent 11 or later) using HTTPS over port 443.

Tip

Aternity gathers and stores detailed performance data. To view older data, it displays a condensed summary (aggregated data), like an hourly or daily summary.

The Agent for End User Devices reports data to Aternity once every minute. If its status becomes disconnected and it cannot send data after trying for five minutes, it locally stores up to 50 minutes of retention data in offline mode, and then sends it when it renews its connection.

The device continuously tries to reconnect to Aternity in ever-increasing intervals, after ½ minute, one minute, two minutes, four minutes, eight minutes, 16 minutes, 32 minutes, and if it still fails, the Agent restarts itself and tries again to connect, restarting this cycle again.

Resource usage

A local Agent in Windows typically uses:

  • CPU: Total utilization across all cores approx. 0.12%. For virtual application servers and MS Terminal Server: typically 5-15%.

  • RAM: Approx. 120MB physical memory (private working set). For virtual application servers and MS Terminal Server, add 40MB per session.

  • Storage: Approx. 110MB, plus Agent log files (10MB to log only errors, or up to 740MB for complete logs). In rare support-led troubleshooting cases, log files can reach up to 3GB.

  • Bandwidth: Network traffic load overhead increases by approx. 0.02 kilobytes per second (KBps) incoming to the device, and approx. 0.05KBps reporting data to Aternity.

Microsoft .NET

Device must have Microsoft .NET v4.5 SP1 or later to use security (TLS 1.2).

Install privileges

You must run the Agent setup with administrator privileges on the device.

Virtual Windows Devices (Running the Windows Agent)

Aternity monitors performance in a wide range of virtual applications and virtual desktops. The virtual servers must be housed in one of the following operating systems:

Attribute Requirement

Virtual server operating system

Windows Server 2016, 2012 R2, 2012, or 2008 R2.

The Windows Agent supports virtual devices and/or virtual applications with any of the following requirements:

Attribute Requirement

Citrix virtual application servers

Citrix XenApp 6.5, 7.6, 7.8, 7.15.

Citrix virtual desktop servers

Citrix XenDesktop 6.5, 7.6, 7.8, 7.15.

VMWare Enterprise VDI

VDI support is for VMWare Horizon View 6.x and 7.x up to 7.2, and support for 7.15. Aternity does not monitor the ESXi hypervisor. VMWare ThinApp is NOT supported.

Microsoft RDC

Microsoft Remote Desktop Services 6.1, 8.1, 10.0.

Microsoft virtual application servers

Microsoft App-V 4.6 SP3, 5.0, 5.1.

Mac Computers (Running the SteelCentral Agent for Mac)

To monitor an Apple Mac with SteelCentral Agent for Mac, it must have the following minimum system requirements:

Attribute Requirement
Agent for Mac

Supported Agent for Mac versions: 2.4, 3.0, 3.1.x

Mac operating system

macOS 10.14 (Mojave) (since version 3.1), macOS 10.13 (High Sierra) (since version 2.4), macOS 10.12 (Sierra), OS X 10.11 (El Capitan), or OS X 10.10 (Yosemite)

Processor

Mac computer with Intel 64-bit CPU.

Resource usage

The Agent for Mac typically uses:

  • CPU: Total utilization across all cores less than 1%.

  • RAM: The SteelCentral Agent for Mac uses approx. 200-300MB of physical memory.

  • Storage: At least 0.5GB free disk space available.
  • Bandwidth: Network traffic load overhead increases by approx. 0.02 kilobytes per second (KBps) incoming to the device, and approx. 0.05KBps reporting data to Aternity.

Monitor web applications

Monitor any web application in any version of Google Chrome released in the past two years. For legacy Agents (on Windows until Agent 9.1.x or on Mac until Agent for Mac 2.3), you must also manually add the Aternity Extension for Chrome to monitor web page load events (WPM) and usage.

Mobile Devices (Running a Monitored Mobile App)

To run a monitored app, the device must have the following operating systems:

Attribute Requirement

iOS operating system of monitored device

iOS 9 or later.

Android operating system of monitored device

Android 4.4 or later.

Embed Mobile Monitoring (Aternity Wrapper and Aternity Mobile SDK)

To add monitoring to a mobile app, you must embed Aternity's monitoring into the app itself, before it is encrypted.

Before embedding Aternity's monitoring into an iOS mobile app, verify your Mac conforms to the following minimum system requirements (Aternity iOS Wrapper and Aternity iOS Mobile SDK):

Attribute Requirement (iOS Wrapper and Aternity iOS SDK)

Operating system

Mac OS X 10.10 or later.

Programming environment

Apple XCode 7 or newer.

Connectivity

Internet access.

App resource usage

When you add Aternity functionality to an iOS app:

  • Disk storage size increases by 3.3MB.

  • RAM size is an extra 5-10MB.

  • CPU usage rises by 1%.

Before embedding Aternity's monitoring into an Android mobile app, verify your device conforms to the following minimum system requirements (Aternity Android Wrapper or Aternity Android Mobile SDK):

Attribute Requirement (Android Wrapper and Aternity Android SDK)

Operating system

Android 4.4 or later.

Java Developer Kit

JDK 1.8 or later.

Programming environment

Google Android Studio or a standalone Android SDK.

Using the SDK Manager, install the latest Android SDK tools (platform tools and build tools) for SDK Platform API level 19 or newer.

Connectivity

Internet access.

App resource usage

When you add Aternity functionality to an Android app:

  • Disk storage barely changes at all.

  • RAM size is an extra 5-10MB.

  • CPU usage rises by 1%.