Aternity Release Notes

Agent for End User Devices 12.1.x

Agent for End User Devices 12.1.x offers new functionality, features and improvements in performance.

Be among the first to try Aternity's enhanced monitoring with the new Agent 12.1.

The Agent for End User Devices monitors end user experience by measuring device and application performance. It is a seamless background utility which runs on each monitored device, and reports its data to Aternity.

You can deploy the Agent throughout your enterprise to collect data from devices and report to Aternity.

Important

Agent 12.1 setup requires 64-bit Windows 7 SP1 or later, or Windows Server 2008 R2 or later operating system. 32-bit is not supported.

Learn more.

Before deploying, see the resolved issues.

Note

Each Agent release incorporates all functionality from earlier releases (of the same major version 12.1).

This article covers the following sections:

Aternity Agent Release States

This section lists different states of Aternity Agent release cycle. The state reflects the stability level of the Agent, and it is not related to functionality. Each Agent release incorporates all functionality from earlier releases (of the same major version 12.1). When the Agent of a certain version changes its state (for example, from CA to GA), its functionality remains the same.

Definitions of Release States for Aternity Agent

Release Candidate (RC) – This is a new Agent version which Aternity intends to make available for customers in the near future. You may request and deploy it to a handful of endpoints to try its features. Please contact Aternity SaaS Admin.

Controlled Availability (CA) – This is a production-ready, supported Agent with which you may start a limited scale rollout to your organization. It's available upon request. Please contact Aternity SaaS Admin.

Early Availability (EA) – This is a production-ready, supported Agent with which any customer may start a tiered rollout to their organization. Please contact Aternity SaaS Administration for full deployment confirmation.

General Availability (GA) – This is a default Agent available for full scale deployment to all environments. For older GA versions, contact Aternity SaaS Admin.

Beta – This is an Agent version which will not become generally available, but you can request it from the Aternity Beta Team and use it to evaluate new features.

What's New in Agent 12.1.4 (General Availability)

Released for General Availability on 30 December 2021

Agent 12.1.4 does not contain new features, but provides enhancements and bug fixes. It includes all functionality from earlier 12.1.x releases.

Validation Tool

PowerShell scripts can now be tested in the PowerShell Validation Tool without being signed.

Security

For increased security, from now, the Agent runs only signed remediation scripts, and PowerShell execution policy no longer allows Unrestricted scripts. ACTION_EXECUTION_POLICY=Unrestricted is no longer supported.

What's New in Agent 12.1.3.95 (General Availability)

Released for General Availability on August 2021

Agent 12.1.3 includes additional security enhancements on top of earlier 12.1.x releases. And of course it includes all functionality from earlier 12.1.x releases.

Security

Aternity Agent for End User Devices security improvements.

What's New in Agent 12.1.2.90 (General Availability)

Released for General Availability on June 2021

Agent 12.1.2 includes security improvements and other enhancements. It includes all functionality from earlier 12.1.x releases.

Security

Aternity Agent for End User Devices security improvements.

Monitoring Enhancements

Supports monitoring of Java applications published using Java OpenJDK Standard Edition 8 (in addition to previously supported Oracle JDK). OpenJDK is a free and open-source implementation of the Java Platform, Standard Edition.

UI Enhancements

Displays application name and version in English, as reported by Aternity Agent and not in a local operating system language. This affects the Application Usage widget and the Application widget in the Troubleshoot Device dashboard, where we display the app name based on the process name.

Monitoring Enhancements

Supports monitoring of the total size of a physical memory installed on the device. You can analyze this attribute in the Device Details dashboard or view it with REST API DEVICE_INVENTORY (learn more). Not all physically installed memory is available for operating system (for example, some memory is allocated to the Display Driver). In such cases, the recorded physical memory may differ from a usable memory. The new Agent records both values: The Total Physical Memory in addition to the usable physical RAM of the device. For managing your organization inventory, you should analyze the Total Physical Memory (a.k.a Installed Memory); in other cases, you might want to analyze the Usable Memory available for applications running on the device.

What's New in Agent 12.1.1.21 (General Availability)

Released for General Availability on April 2021

Agent 12.1.1.21 includes security improvements. It also includes all functionality from earlier 12.1.x releases.

Security

Aternity Agent for End User Devices security improvements.

What's New in Agent 12.1.1.13 (General Availability)

Released for General Availability on 02 December 2020

This Agent release incorporates all functionality from earlier releases described below in this document as well as all functionality from Agent 12.0.6. In addition, it also includes the following enhancements:

MS Teams Monitoring

(SaaS only) Supports reporting on the scheduled calls in MS Teams (also referred to as Meetings in MS Teams UI).

What's New in Agent 12.1.0.446 (Controlled Availability)

This Agent release incorporates all functionality from earlier releases described below in this document. In addition, it also includes the following enhancements:

Note

This Agent release remains at the Controlled Availability stage and will not be promoted to the General Availability stage. There is another version (see above) that incorporates all functionality from the current release.

Monitoring Enhancements

Supports reporting on user installed applications (per user account, and not only per device).

Recording Enhancements

Supports recording activities in Microsoft's Chromium-based Edge browser.

Recording Validation Enhancements

Supports filtering Incomplete activities in the Recorder’s Validation Summary window. Select to view or deselect to hide the Incomplete activities.

Monitoring Enhancements

For monitored devices, supports monitoring of File Downloads for the files on the white list pages.

Monitoring Web Applications in the New Microsoft Edge

Aternity automatically monitors the performance of web applications in the new Microsoft Edge, a Chromium-based browser. Correlate the performance of custom activities or page load activities with different browsers: Chrome, IE, FireFox, and Chromium-based Edge. Diagnose web application performance issues proactively.

Analyzing Microsoft Teams (SaaS only)

With Agent for End User Devices 12.1, you can monitor Microsoft Teams. To get the Agent, please contact Aternity Beta Team. Aternity provides the new capability to monitor and report on the calls in Microsoft Teams and introduces the new advanced dashboard for analyzing those calls. This dashboard includes many call-specific measurements and advanced attributes. Learn more. Get to know your users' experience with MS Teams for optimizing employees collaboration. Improve meeting audio/video quality in your organization. Learn more about attributes and measurements Aternity collects. Learn how to enable the integration of Aternity with Microsoft Teams.

File Downloads Monitoring in Google Chrome

With Agent for End User Devices 12.1, you can analyze file downloads quality in Google Chrome. Use the new File Downloads (Advanced) dashboard for your analysis. See the file transfer time, speed, or size and its impact on efficiency in your organization. Customize the dashboard to show the relevant information to your business. To get Agent 12.1, please contact Aternity Beta Team Learn more.

Aternity Web Activity Creator (WAC 2.0)

With Agent for End User Devices 12.1, you can monitor the activities created with WAC 2.0. To get the Agent, please contact Aternity Beta Team. The Aternity Web Activity Creator (WAC) enables you to quickly and intuitively create custom activities for web applications directly from the web page. The WAC is an interactive Google Chrome extension that opens as a floating sidebar next to your web page. It offers a simple workflow to create your custom activities all on one PC. With WAC 2.0, you can design and monitor your activities within Internet Explorer in addition to Google Chrome. WAC 2.0 provides extensive collaboration capabilities. It allows different users from the same account to view and edit the same activity. In addition, WAC 2.0 allows indicating the end of a business activity upon multiple events. You can complete an activity on any event or on multiple events you indicate. To do this, apply the And condition. This means that only when all the events completed, then the activity state becomes Complete. You can apply And or Or conditions to complete events.

Enhanced Monitoring

Supports reporting of available PRC information for protected processes (like CPU and IO Read/IO Write, but Memory PRC is unavailable).

Enhanced Monitoring

Supports new attributes, including Battery Capacity Health, BIOS, and SCCM.

Operating System support

Supports 64-bit operating systems only.

Security Protocols

When sending data, the Agent reports securely to Aternity via HTTPS. For Agent for End User Devices 12.1 or later: Device must have Microsoft .NET v4.6 SP2 or later to use security (TLS 1.2). Note that TLS 1.1 is deprecated.

If you are interested in this functionality, contact Aternity SaaS Admin to get the setup files.

Original source

Agent for End User Devices 12.1.x offers new functionality, features and improvements in performance.
Tip
This release includes all resolved issues from Agent 12.0.x.
For information about the new features of Agent 12.1, see What's New in Agent 12.1.x for Windows (End-of-Support).

Deploying This Upgrade
You can deploy the Agent throughout your enterprise to collect data from devices and report to Aternity.

Known Issues
MS Teams monitoring may cause an increased disk IO activity while calls are made. DEM-7740
On Windows 11, Agent for End User Devices cannot report the correct Server Name and/or IP. Thus, in the advanced dashboards: For Web applications, you may see the domain name instead of the actual Server Name and Server Hostname. For Desktop applications, you may see the IP instead of the actual Server Name and Server Hostname. DEM-7866
The Recorder does not properly work when recording on a device with a non-English operating system using Agent 12.1.3. Please contact Riverbed Support Team for guidance how to resolve the issue. DEM-5963
When monitoring MS Teams on multisession devices (WVD), some calls are missing due to fast reuse of PID. DE24172
Two separate instances of the Agent appear under Installed Applications when installed twice, by running MSI and EXE files, (instead of being upgraded). DE23745
An error message might pop up when uninstalling the Agent 12.1 beta 2. DE23507
Failing to detect the PowerShell scripts timeout in Remediation and other scripts. DE2550 and DE2579

Limitations
Aternity Agent 12.1.3 and later
Recorder may fail to record on certain devices. If this happens, please contact Riverbed Support Team.

Issues Resolved in This Release
Each Agent release includes all fixes from all previous updates.
Security Fix for high severity vulnerability CVE-2022-43997, identified by Jack Ullrich of SpecterOps DEM-14223 N/A 12.1.4.27
Resolved a case where Agent was not reporting MS Teams Group calls. DEM-6621 SF89996 12.1.4
Resolved a case when Agent 12.1.3 fails to record while a device is connected to the Appgate VPN. DEM-7111 SF90240 12.1.4
Resolved a case where Agent 12.1.3 uninstall failed if Recorder was enabled. DEM-6737 N/A 12.1.4
Resolved a case where application installation time was reported in UTC instead of local time zone. DEM-3704 N/A 12.1.4
Resolved a case where PowerShell scripts timeout was not enforced. DEM-2579 N/A 12.1.4
PowerShell scripts can now be tested in the PowerShell Validation Tool without being signed. DEM-2343 N/A 12.1.4
For increased security, PowerShell execution policy no longer allows Unrestricted scripts. DEM-1987 N/A 12.1.4
Resolved a case where Aternity logs in Chrome debugging tool were turned on by default and created additional load on the browser. DEM-2379 SF87020 12.1.4
Resolved a case where System Crash (BSOD) details were not reported. DEM-1753 N/A 12.1.4
Agent security improvements. DEM-6768 N/A 12.1.3.95
Agent security improvements. DEM-5264 N/A 12.1.3.95
Agent security improvements. DEM-2647 SF87284 12.1.2.90
A180AG.exe experienced an unhandled exception when performing the WiFi data collection. (A180AG.exe is the Agent's core process, performing most of the data collection, operations, and configuration.) DEM-1453 N/A 12.1.2.86
Resolved a case of missing calls monitoring and high CPU when using MS Teams on multisession devices (WVD). DE24159 SF86103 12.1.2.76
Resolved a case of an occasional failure in monitoring EventLog on weak VDI devices (devices with low resources compared to the average standard). DE23898 SF85237 12.1.2.76
Resolved a case of an occasional failure in monitoring of virtual network adapters (VPN). DE23947 SF84982 12.1.2.76
Resolved a case of missing device attributes due to multiple reported values (for example, Last Boot could be missing). DE24055 N/A 12.1.2.76
Resolved Registry and Files System namespace usage in PowerShell Scripts to use 64-bit namespace instead of WOW64. Note that the issue does not affect the Validation utility. DE23991 N/A 12.1.2.76
Agent security improvements. N/A N/A 12.1.1.21
(SaaS only) Resolved a case of not reporting on the scheduled calls in MS Teams (also referred to as Meetings in MS Teams UI). N/A N/A 12.1.1.13
Resolved a case when some applications were being reported as device installed applications rather than user applications (installed per user account). DE23744 N/A 12.1.1.13
Resolved a case when deleting local files while canceling remediation actions failed. DE23655 N/A 12.1.1.13
Resolved a case of a memory leak in the Aternity Agent during Network Discovery monitoring. DE23742 N/A 12.1.1.13
Resolved a case of missing reports on MS Teams calls performed on resource constrained machines (for example, virtual machines). DE23854 N/A 12.1.1.13
Resolved a case of security vulnerabilities in Aternity Agent’s Assistant Service. US12625 SF1313694 12.1.0.446
Resolved a case of security vulnerabilities in the Remediation feature. DE23643, DE23683 N/A 12.1.0.446
Resolved a case of a failure to run and get reports on Firefox for WAC designed activities. DE23408 N/A 12.1.0.446
Resolved a case when a cleanup of JAVA_TOOL_OPTIONS failed. DE23566 N/A 12.1.0.446
Resolved a rare case of monitoring failure due to recycling process ID (PID) issues. DE22665 N/A 12.1.0.446
Resolved a case of Agent high CPU consumption due to Microsoft Teams monitoring. DE23347 N/A 12.1.0.397
Temporarily, you cannot open the recorded files. DE23272 N/A 12.1.0.397
Resolved a case of nested Microsoft Teams calls that were not reported: When the second call was answered while the first one put on hold, the second call was not reported. DE23347 N/A 12.1.0.397
Resolved a case of Microsoft Teams calls that were not reported due to users' status (Away, Busy, and others). DE23324 N/A 12.1.0.397
Resolved a case where Microsoft Teams calls were not reported after logging out and logging in again. DE23444 N/A 12.1.0.397
Resolved a case when Agent repeatedly tried to run unsigned scripts. DE23191 N/A 12.1.0.397
Resolved a case where the Agent did not report Microsoft Teams calls with multiple participants. N/A N/A 12.1.0.358
The Agent's A180PowerShellCollector process sometimes crashes when the script encounters unhandled exceptions on unmanaged threads (MS Windows limitation). There is no functional impact on Aternity. DE23297 N/A 12.1.0.358
Resolved a case where the Agent reported the same measurement of the same health event twice. DE21604 SF1318959 12.1.0.358
Resolved a rare case where HTTP authentication through a proxy server failed. It happened only in a rare case where the hostname starts with HTTP like http://http-proxy.defect.com. DE23295 SF1319581 12.1.0.358
Resolved a case where the Agent failed to report the updated type of a device (for example, after changing it from laptop to tablet). DE21872 SF1157077 12.1.0.1348
Resolved a case of a high CPU consumption in Internet Explorer caused by multiple HTTP activities with regex conditions that include wildcards. DE22772 SF1299870 12.1.0.1348
Resolved a case of a missing property in Internet Explorer page destroyed event, which caused some activities to fail. DE20880 N/A 12.1.0.1348
Resolved a case of missing reports for error pages in Google Chrome (with the HTTP error code 4xx or 5xx). DE22279 N/A 12.1.0.1348

Original source

Aternity provides real-time insights and automated remediations for Intel Thunderbolt and WiFi issues.

Riverbed Aternity leverages its Intel partnership to deliver real-time visibility into Thunderbolt™ peripherals and WiFi connectivity, configuration, and performance.

Aternity provides below-the-OS-metrics visibility. Combining Intel’s metrics with Aternity's real-time data collection and analysis, IT can proactively identify and resolve digital experience issues.

Learn more

What's New in the Intel Module 2.50.1 (GA)

This release includes the following enhancements:

Feature Description USB Peripheral Connectivity Errors improvements Now reports USB Vendor name and Product Name in addition to Vendor ID and Product ID

Deploying This Upgrade

Important

Unified Agent is the only way to deploy and distribute the Intel Module 2.50.1 release.

The Intel Module 2.50.1 release requires Aternity Module 25.1.0.13 or higher.

The Riverbed Unified Agent is a versatile container component designed to simplify the deployment, upgrade, and management of Riverbed modules (formerly called as agents) for our valued customers.

With the Unified Agent, you can conveniently deploy different modules (for Windows, Mac, or Linux devices) directly from within the UI, streamlining your workflow and enhancing efficiency.

First, read carefully about software system requirements.

Then, learn how to install the Unified Agent and its module.

Supported Use Cases

This release supports the following use cases:

Field Description USB Peripheral Connectivity Errors Detects connectivity issues with peripherals (such as cameras, mice, and keyboards) and categorizes them by device type and manufacturer Thunderbolt Connectivity Errors Detects connectivity issues with Thunderbolt peripherals Thunderbolt External Screen not Displaying Detects when a user connects their laptop via USB-C to an external display but no output occurs WiFi Disconnected Antenna Detects if a WiFi card in the laptop has one of its antennas disconnected WiFi Suboptimal Driver Property Monitors and remediates when WiFi driver settings on Intel wireless network cards do not align with Intel’s recommended configuration WiFi Bad Coverage Detects when a device has poor WiFi coverage with specific resolutions for home-based and office-based users WiFi Technology Gap Helps network and infrastructure administrators identify access points (APs) that are outdated for the laptop fleet they support. WiFi Roaming Report Provides tracking of all roaming events in the WiFi infrastructure including failures, roaming reasons and RSSI values. WiFi Co-Channel Interference Provides tracking of when laptops determine there is interference on the 5GHz WiFi band with other nearby APs WiFi Non Friendly Channel Usage Provides tracking of when laptops determine there is interference with APs running on optimal 2GHz channels (1, 6 or 11) from access points on non-friendly channels (2-5 or 7-10) WiFi High AP Utilization Identifies when access points are running with high channel utilisation along with the station count and RSSI of laptops connecting to those APs

Issues Resolved in This Release

Description Resolved In Improved reporting of WiFi Bad Coverage event in some edge cases, related to underlying issues in Platform Power State conditions (S3/S4/S5, Suspend, Resume) 2.50.1 All monitors received every event instead of only the module subscribed to it, resulting in increased resource consumption 2.50.1

Known Issues in This Release

Description

When using Aternity Module 25.1.0.13, an Aternity Module that starts while the Intel Module is down won't report Intel events until the next Aternity Module configuration.

When using Aternity Module 25.1.0.13, the Aternity Module may have high CPU consumption due to Intel Module initialization failure following a machine restart.

Release States

This section lists different states of the release cycle. The state reflects the stability level of the module only, and not related to functionality. When the module changes its state (for example, from CA to GA), its functionality remains the same.

Release Candidate (RC) – This is a new version which Riverbed intends to make available for customers in the near future. You may deploy it to a handful of endpoints to try its features.

Controlled Availability (CA) – This is a production-ready, supported module with which you may start a limited scale rollout to your organization.

General Availability (GA) – This is a default module available for full scale deployment to all environments.

Original source

Aternity Agent for Mac

Aternity Agent for Mac offers the ability to gather device metrics and performance of managed and discovered native desktop applications and web applications running on Apple Mac computers.
Aternity Agent for Mac works with both Aternity SaaS and on-premise.
About the new Module for MacOS, learn here.

Monitor Macs with the Aternity Agent for Mac

Aternity Agent Release States

This section lists different states of Aternity Agent release cycle. The state reflects the stability level of the Agent, and it is not related to functionality. When the Agent of a certain version changes its state (for example, from CA to GA), its functionality remains the same.

Definitions of Release States for Aternity Agent

• Release Candidate (RC) – This is a new Agent version which Aternity intends to make available for customers in the near future. You may request and deploy it to a handful of endpoints to try its features. Please contact Aternity SaaS Admin.
• Controlled Availability (CA) – This is a production-ready, supported Agent with which you may start a limited scale rollout to your organization. It's available upon request. Please contact Aternity SaaS Admin.
• Early Availability (EA) – This is a production-ready, supported Agent with which any customer may start a tiered rollout to their organization. Please contact Aternity SaaS Administration for full deployment confirmation.
• General Availability (GA) – This is a default Agent available for full scale deployment to all environments. For older GA versions, contact Aternity SaaS Admin.
• Beta – This is an Agent version which will not become generally available, but you can request it from the Aternity Beta Team and use it to evaluate new features.

Enhancements in Agent for Mac 4.5.0 (GA)

Released as General Availability in March 2026
Agent for Mac 4.5.0 provides the enhancements described below:

• Support for jamfconnect to retrieve User Full Name and Email address from the Agent.
• Report OnVPN static attributes.
• Report FreeDiskSpace and TotalDiskSpace static attributes.
• Supports macOS 26 (Tahoe), 15 (Sequoia), 14 (Sonoma) 13 (Ventura).

View resolved issues in this release.

Enhancements in Agent for Mac 4.4.0 (GA)

Released as General Availability in November 2025
Agent for Mac 4.4.0 is a maintenance release that adds support for Aternity Digital Assistant for Mac 1.0 but otherwise includes only bug fixes:

• Supports macOS 26 (Tahoe), 15 (Sequoia), 14 (Sonoma) 13 (Ventura).

macOS 12 (Monterey) is no longer supported.

View resolved issues in this release.

Enhancements in Agent for Mac 4.3.0 (GA)

Agent for Mac 4.3.0 provides the enhancements described below:

• Supports macOS 15 (Sequoia), 14 (Sonoma) 13 (Ventura), 12 (Monterey), 11 (Big Sur)
• New out-of-the-box health events:
  • Low Disk Space
  • Thermal State Health Event
  • Memory Pressure Health Event
  • Battery Health Event
  • Storage Device Health Event
• Custom Device Health Events
  • Detect any arbitrary error condition via shell script and report a new type of health event.

View resolved issues in this release.

Enhancements in Agent for Mac 4.2.4 (SaaS only) (GA)

Agent for Mac 4.2.4 provides the enhancements described below:

• Supports macOS 15.2 Sequoia

View resolved issues in this release.

Enhancements in Agent for Mac 4.2.3 (SaaS only) (GA)

Agent for Mac 4.2.3 is a maintenance release and contains only bug fixes. The Agent includes all functionality from previous Agent releases.

View resolved issues in this release.

Enhancements in Agent for Mac 4.2.2 (GA)

Agent for Mac 4.2.2 is a maintenance release and contains only bug fixes. The Agent includes all functionality from previous Agent releases.

View resolved issues in this release.

Enhancements in Agent for Mac 4.2.1 (RC)

Mac Agent 4.2.1 contains bug fixes. The Agent includes all functionality from previous Agent releases.

View resolved issues in this release.

Enhancements in Agent for Mac 4.2.0 (RC)

Mac Agent 4.2.0 provides the enhancements described below:

• Native support for Apple silicon
• The Agent for Mac is now a full macOS application installed under /Applications
• Feature parity with the 3.7 Agents for Mac
• Supports MacOS 14.1 (Sonoma), MacOS 13.0 (Ventura), MacOS 12.0 (Monterey), 11.0 (Big Sur), and 10.15 (Catalina)
• Supports Chrome extension Manifest V3
• Supports web metrics collection, including web usage and page loads:
  • Web usage reporting
  • Page load monitoring
  • Web page monitoring
  • Web activities

Before deploying, view resolved and known issues in this release.

Enhancements in Agent for Mac 4.0.1 (SaaS only) (GA)

Mac Agent 4.0.1 has been released for general availability and provides new features and enhancements:

• Supports MacOS 13 (Ventura), 12.0 (Monterey), 11.0 (Big Sur), and 10.15 (Catalina)
• Native support for Apple Silicon and Intel chips
• Better performance (CPU and memory) on Apple Silicon and Intel
• Eliminate need on Python for installation
• Eliminate deprecated tools/commands in scripts
• This Agent collects only device metrics. Web usage, page loads and web activities are planned to be part of future releases.

Before deploying, view known issues in this release.

Original source

Aternity continuously evolves through frequent updates, delivering a stream of fresh functionality, improved features, and updated dashboards. In addition to our main monthly updates, Aternity introduces new features dynamically throughout the month as part of our agile CI/CD development process. Stay informed about these innovations by regularly checking our live feed ( ), where new features are promptly listed upon integration. Make it a habit to revisit this page frequently to stay ahead of the curve and explore the latest enhancements to elevate your Aternity experience.

Tip

These features will be rolled out on the SaaS environments as per our release schedule. If you don't see these features in your Aternity console yet, please be patient as your system will be upgraded soon.

This article lists the latest updates to Aternity SaaS in 2026. You can also view Aternity updates from previous years.

New Features and Capabilities Released During April 2026

The scheduled April release provides system maintenance and internal bug fixes to enhance performance and stability.

New Features and Capabilities Released During March 2026

The scheduled March release provides system maintenance and internal bug fixes to enhance performance and stability.

Aternity Module release 26.3 (RC) offers the enhancements for Troubleshoot Device dashboards

New out-of-the-box Citrix monitoring package, including a set of new data collections and supporting Troubleshoot Device dashboard tab. New Citrix Static Attributes Collection, including: Desktop groups (registry oriented) Catalog Name (the deployed image) Hypervisor Name Desktop Kind (private or shared) New Citrix Monitored Attributes Collection, including: ICA RTT HDX Encode Time Thinwire I/O Average FPS Session Logon Measurement and Breakdown These metrics are also available in the Advanced Dashboard and through the REST API OS Arch detection (Added Arm64) Security and performance enhancements

Service Desk Alerts for Mobile Devices Health Events

Service Desk Alerts can now be created using Mobile Devices Health Events. This allows for example to associate runbooks or create ServiceNow tickets automatically to events generated by Android or iOS devices the same way it is done for windows and MacOS. Learn more.

Microsoft Teams solution pack

You can now see a user’s Microsoft Teams call quality in-depth in new dashboards. Search for a given user and view their call quality on the Microsoft Teams Calls tab, then drill-down into any specific call for more details, including relevant business activities and health events that happened during the call.

A new role, View MS Teams package dashboards, controls access to the dashboards and must be granted to users before they can see these screens.

5 new predefined business activities have been added for Microsoft Teams:

• Join Meeting
• Rejoin Meeting
• Share Screen
• Start Video
• We could not connect to the internet

These 5 business activities are the most beneficial for identifying user experience issues during calls that are not directly related to call quality. Repeated occurrences of Join Meeting, Rejoin Meeting, Share Screen or Start Video suggest client-related issues related to joining calls or starting specific streams.

Learn more about predefined activities.

Learn more about MS Teams call quality.

Learn more about MS Teams call details.

Aternity Digital Assistant 24.11.0.174 supports .NET9 and .NET10

Aternity Digital Assistant 24.11.0.174 now supports .NET8 or later.

New Features and Capabilities Released During February 2026

New Release 3.3 of Aternity App for ServiceNow with Interaction support

Aternity ServiceNow integration now supports Interactions, bringing powerful troubleshooting and remediation capabilities earlier into the service workflow.

Service Desk Agents can now investigate and resolve user issues directly from Interactions using remediation actions, real-time device data, and quick links to Aternity dashboards. This capability reduces unnecessary incident creation and accelerates time to resolution.

Learn More.

New Features and Capabilities Released During January 2026

The scheduled January release provides system maintenance and internal bug fixes to enhance performance and stability.

Original source

The Riverbed Unified Agent is a versatile container component designed to simplify the deployment, upgrade, and management of Riverbed modules (formerly called as agents) for our valued customers. With the Unified Agent, you can conveniently deploy different modules (for Windows, Mac, or Linux devices) directly from within the UI, streamlining your workflow and enhancing efficiency.

This article lists the latest updates to the Unified Agent for MacOS.

What's New in Unified Agent 26.4 (GA)

This Unified Agent allows deploying modules for MacOS and monitoring MacOS devices.

Original source

This document provides a comprehensive table of feature enhancements, organized by version (including release state) and feature description.

The Aternity Module for MacOS (formerly known as Aternity Agent for Mac) monitors end user experience by measuring device and application performance. It is a seamless background utility which runs on each Mac monitored device, and reports its data to Aternity.

What's New in Aternity Module for MacOS 26.4 (GA)

Released for General Availability in March 2026

This module allows monitoring MacOS devices using the Riverbed Unified Agent.

Deploying the Upgrade

Important

Unified Agent is the only way to deploy and distribute the Aternity Module.

The Riverbed Unified Agent is a versatile container component designed to simplify the deployment, upgrade, and management of Riverbed modules (formerly called as agents) for our valued customers. With the Unified Agent, you can conveniently deploy different modules (for Windows, Mac, or Linux devices) directly from within the UI, streamlining your workflow and enhancing efficiency.

First, read carefully about software system requirements.

Then, learn how to install the Unified Agent and its module.

Release States

This section lists different states of the release cycle. The state reflects the stability level of the module only, and not related to functionality. When the module changes its state (for example, from CA to GA), its functionality remains the same.

Release Candidate (RC) – This is a new version which Riverbed intends to make available for customers in the near future. You may deploy it to a handful of endpoints to try its features.

Controlled Availability (CA) – This is a production-ready, supported module with which you may start a limited scale rollout to your organization.

General Availability (GA) – This is a default module available for full scale deployment to all environments.

Original source

This document describes the necessary procedures for upgrading to Application Server 2025.10.
With version 2025.6+, APM is introducing a cleaner, more secure, and future-ready platform based on AlmaLinux 9. The new one-step upgrade process via appinternals_upgrade_env makes the transition seamless while preserving your existing environment (no configuration loss, no rework, and no manual cleanups).
Important Information Before Upgrading
Review the following important guidelines and prerequisites to ensure a smooth and successful upgrade process.
Backup Recommended : While the process is designed to preserve all data and configurations, we advise taking a backup for safety.
Expected Downtime : The system will briefly restart services during the upgrade.
Preserved Configurations : iptables rules, network settings, and service configurations remain intact.
No Additional Upgrader Needed : Customers do not need to run a separate upgrade command for the software, it is handled by upgrader_new .
Upgrade to Application Server 2025.10 from CentOS7
If APM has been deployed on a CentOS7 system, it will be necessary to upgrade the operating system release before upgrading APM.
The OS upgrade process is described in the resources listed below:
CentOS 7 to Red Hat 8 (How to convert CentOS Linux to Red Hat Enterprise Linux)
CentOS 7 to Alma 8 (How to migrate from CentOS 7 to AlmaLinux 8)
CentOS 7 to Rocky 8 (How to migrate from CentOS 7 to Rocky Linux 8)
Post OS upgrade, it will be necessary to upgrade the APM runtime environment (LRE).
LRE OS Upgrade
Starting with software version 2025.6+, the LRE (Limited or Restricted Environment) used by APM platform will be upgraded from CentOS 7 to AlmaLinux 9.
This update ensures improved long-term support, enhanced security, and compliance with current Linux ecosystem standards, as CentOS 7 has reached its end of life (EOL).
To complete this upgrade, customers must use a new tool included in the release package. This utility will automatically upgrade both the LRE OS and the core software to version 2025.6+
Single-Step Upgrade
Customers upgrading to version 2025.6+ must follow a new process using the provided installer script appinternals_upgrade_env . The process includes:
Upgrading the LRE from CentOS 7 to AlmaLinux 9.5
Automatically upgrading the software to version 2025.6+
This method replaces the older upgrade flow and ensures a consistent, clean environment post-upgrade.
No data loss or configuration changes
No reconfiguration required
iptables and system integrations preserved
Upgrade Instructions
Follow these steps to perform the upgrade:

1. Download the upgrade package, the tarball named: appint-linux-2025.6.1.4.tar
2. Switch to a terminal and ensure you are running as sudo . All upgrade steps must be executed with elevated privileges.
3. Extract the downloaded tarball: tar -xvf appint-linux-2025.6.1.4.tar
4. Run the upgrade script. Navigate to the extracted directory and execute the installer: cd /tmp
   sudo ./appinternals_upgrade_env
   For example:
   [root@003 tmp]# ./appinternals_upgrade_env
   Upgrade will remove current AppInternals binaries and replace with new
   Data will be preserved.
   Proceed ? (y/n) : y
   2025/04/22 13:14:17 Verify.go:21: Verifying install
   2025/04/22 13:14:17 Verify.go:36: Verify OK
   2025/04/22 13:14:17 main.go:234: Shutting down AppInternals...
   2025/04/22 13:15:27 main.go:237: Shutdown done
   2025/04/22 13:15:31 main.go:244: Upgrading from image 'appint-image-2025.6.1.4.txz'
   2025/04/22 13:15:31 main.go:75: Unpacking tar...
   2025/04/22 13:17:03 main.go:110: Unpack done
   2025/04/22 13:17:04 main.go:135: Removing host rpm appint-linux-host
   2025/04/22 13:17:04 main.go:140: rpm remove done
   2025/04/22 13:17:04 main.go:120: Updating host rpm appint-selinux-2025.6.1-4.noarch.rpm
   2025/04/22 13:17:30 main.go:125: rpm update done
   2025/04/22 13:17:30 main.go:120: Updating host rpm appint-linux-host-2025.6.1-4.x86_64.rpm
   2025/04/22 13:17:32 main.go:125: rpm update done
   2025/04/22 13:17:32 main.go:268: Syncing file system
   2025/04/22 13:17:42 main.go:154: System is now being rebooted...
   Tested Versions
   The following versions have been tested using the new upgrader:
   The script will:
   Replace the CentOS 7-based LRE with AlmaLinux 9
   Automatically migrate necessary configurations, services, rules, etc.
   Upgrade the installed software to version 2025.6+
   Restart services, reboots as needed.
   No additional manual steps are required once the script completes.
   Tested Versions
   2025.3.0.14
   2024.10.1.2
   2023.7.0.39

Original source

You can define a webhook for Aternity APM and then use it to send alerts. A webhook is a URL that APM POSTs alert data to when alerting criteria is met.

A remote service, such as ServiceNow, can define webhooks. A webhook is often defined by:

• The webhook URL
• The authentication data
• The data processed by the webhook

Procedure

Step 1 To configure a webhook, select the Gear Icon > Webhooks and then select the plus icon next to Define a webhook recipient to open the screen.

Enter all required details to define a webhook

In this example, webhook will POST to https://10.45.200.97/webhooks/alert when invoked. Currently, Aternity APM webhook implementation supports HTTP basic authentication only. The service that defines the webhook should supply the required user name and password.

HMAC Shared Secret is a message validation scheme supported by some webhook implementation services. If supplied by the service, this value should be filled in.

Step 2 Ensure HTTPS certificate validation.

If the webhook URL is HTTPS based, then make sure that Aternity APM is able to validate the server's TLS Certificate. If the server certificate is self-signed or unrecognized by one of the major certificate providers, then select Allow Insecure TLS. This option skips the HTTPS certificate check while connecting to the server. We strongly recommend, however, using valid certificates in your production environments.

Step 3 Test the webhook access by selecting the Send Test button.

Now the command attempts to POST a short test string to the server defined with the webhook URL. If sending a POST request to the URL fails, you may see an error message similar to the following:

View the error message and fix the problem

This error means that there is no server running at 10.45.200.97 or the APM server does not have a route to 10.45.200.97.

There are two types of errors, Communication and Security:

Communication errors:

• Server is not up or no path to host
• The URL is wrong

Security errors:

• The user name / password is wrong
• The Web Hooks server does not support HTTP Basic
• HTTPS setup fails - try testing with ‘Allow Insecure TLS’

Tip

Returned error messages may be unclear. If possible, it is recommended to check the webhook server and to see if there are log messages created by the APM server.

Step 4 (Optional) You will probably need to create firewall rules or whitelist the outgoing gateway public IP ranges corresponding to your SaaS environment to be able to receive webhook HTTP requests. The SaaS environment IP ranges are documented in Arternity APM SAAS Gateway Public IP List located on Aternity Support Site.

Tip

Webhooks send Dynamic Alerts data. A review of Dynamic Alerts is beyond the scope of this article. Here is an example of the JSON POSTed to a webhook. Your system will receive a JSON with the following format:

{
  "alert_type": "set", 
  "metric_unit": "ms", 
  "plot_image": "...", 
  "dimension_name": "transaction", 
  "violations_end_time": 1669922904, 
  "dampening_minutes": 2, 
  "severity": "MINOR", 
  "violations_desc": "Test violation", 
  "current_value": 10, 
  "dimension_value": "999", 
  "metric_operation": "o1", 
  "alert_definition_id": 16, 
  "threshold_type": 0, 
  "trigger_time": 1669922904, 
  "violations_start_time": 1669922904, 
  "metric_name": "metric name", 
  "analysis_server_hostname": "my-apm.aternity.com", 
  "current_value_time": 1669922904, 
  "duration_seconds": 100, 
  "url": "https://my-apm.aternity.c/url", 
  "analysis_server_ip": "10.xx.xx.xxx", 
  "analysis_server_version": "202x.xx.0

Original source

This article describes the new unattended agent deployment

This is an optional deployment mode that facilitates the onboarding of uninitiated users to the Aternity APM platform. The unattended agent installation takes less than a couple of minutes to have your server reporting on the Agent List page.

The Install agent page was modified to include a new command line that should be copied and pasted on Windows and Linux servers to automatically install and start the agent.

Note

The unattended installation is intended for non-CloudNative environments.

Prerequisites

This deployment mode requires the following:

• server network access to
  • *.steelcentral.net (HTTPS)
  • *.aternity.com (HTTPS)
• administrator privileges:
  • the user running the script has to have admin rights
• Linux-specific
  • bash
  • curl
  • gunzip
• Windows-specific
  • PowerShell

Getting Started

To deploy the agent, copy the command line of the unattended agent installation and paste it to your server’s terminal.

Copy the command line

See here the command line for Linux installations:

curl -fsS https://*/install-agent.sh | \
        SAAS_ANALYSIS_SERVER=agents.apm.my-env.aternity.com \
        SAAS_CUSTOMER_ID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx \
        RELEASE=atny-saas/saas-latest \
        bash

This will perform three main actions:

Field Description

Download the agent setup script by using the following command:

curl -fsS https://*/install-agent.sh

Specify settings for the setup script

SAAS_ANALYSIS_SERVER=agents.apm.my-env.aternity.com 
                SAAS_CUSTOMER_ID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx 
                RELEASE=atny-saas/saas-latest

Runs script which will do the following:

1. Downloads the agent installer
2. Creates settings for the setup script
3. Runs the silent setup

Advanced Options and Tasks

If one or more of the prerequisites is not satisfied, or you need an advanced deployment, use the Standard installation (download of the binary installer) or follow one of the modified steps described in this section.

The unattended installation is supported on on-premise deployments, however, the script downloads the agent installation binary from our SaaS by default. For a self-contained deployment, follow instructions for “limited or no internet connection” below.

Unprivileged Installation (No Admin Rights)

The user executing the install-agent script should have privileges to execute the script and install software. This can be done by a non-root user if they are permitted in the sudoers file.

On Linux, the agent is installed as the same user who executes the install-agent script. By default this is $(whoami). A different user can be specified via the USERACCOUNT environment variable. For example:

curl -fsS https://*/install-agent.sh | \
        SAAS_ANALYSIS_SERVER=agents.apm.my-env.aternity.com \
        SAAS_CUSTOMER_ID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx \
        RELEASE=atny-saas/saas-latest \
        USERACCOUNT=aternityuser \
        bash

On Windows the agent is installed as the current user, $env:UserName. To install as a different user you cannot use the install-agent script and should instead following the unattended installer instructions where specifying the O_SI_USERACCOUNT option is available.

Environments with proxy

For adding proxy support you will have to download the install script and the installer binary manually to be able to change the script and add the proxy settings (O_SI_PROXY_SERVER_*) as described here.

Environments with Limited or No Internet Access and Other Special Cases

For environments with no or limited internet access, the script or the installer binary downloads will fail. There are two workaround options in this case:

• Use the “standard” installation. See instructions here
• Modify the script to point the installer_filepath variable to the installer binary. This requires to download manually in advance the script and the binary.

This applies for other special cases as:

• changing the temporary folder
• changing the target installation folder
• and more...

Original source

Analysis Server

Analysis Server is the central APM component that stores and processes performance data generated by web pages and Agent systems you want to monitor. The Analysis Server also provides the web interface for users to analyze data it collects. It is included as part of the APM virtual appliance or installed on a dedicated Linux system.
This article lists features and enhancements in APM Analysis Server as well as bug fixes.

APM Server 2025.10.0 (on-premise) - February 2026 Release

2025.10.0 is an APM on-premise Server GA release.
This is a major release containing bug fixes, security fixes and performance enhancements, including:

• Switch Application Server backend to RHEL9 as base distribution
  APMDEV-7836
  2025.10.0
• Upgraded OpenSSL 3.2 to 3.2.3 to address CVE-2024-5535
  APMDEV-7986
  2025.10.0
• Updated Content-Security-Policy headers
  APMDEV-8020
  2025.10.0
• Fix for POD crashes in Production when using Agentless mode
  APMDEV-8052
  2025.10.0
• Import and Export Configuration is not creating necessary configuration JSON files in psockets/userdata/config
  APMDEV-8054
  2025.10.0
• Update library libcurl to v8.16+ to address CVE-2025-10148
  APMDEV-8077
  2025.10.0
• Validate Alpine Linux versions and identify any dependencies
  APMDEV-8084
  2025.10.0
• Instrumentation option does not persist when we migrating to APM Application Server 2025.6
  APMDEV-8104
  2025.10.0
• Configuration override text box syntax check for JSON validation not functional
  APMDEV-8122
  2025.10.0

How to Upgrade to Application Server 2025.10 from CentOS7

If APM has been deployed on a CentOS7 system, it will be necessary to upgrade the operating system release before upgrading APM. Learn more.
The OS upgrade process is described in the resources listed below:

• CentOS 7 to Red Hat 8 (How to convert CentOS Linux to Red Hat Enterprise Linux)
• CentOS 7 to Alma 8 (How to migrate from CentOS 7 to AlmaLinux 8)
• CentOS 7 to Rocky 8 (How to migrate from CentOS 7 to Rocky Linux 8)

Post OS upgrade, it will be necessary to upgrade the APM runtime environment (LRE).
Refer to the detailed upgrade instructions.

APM Server 2025.6.0 (on-premise) - June 2025 Release

This release contains vulnerability updates and bug fixes, including:

• Updated OpenJDK to jdk-17.0.15
  APMDEV-7967
  2025.6.0
• Removed TLS version 1 for psockets on port 7090
  APMDEV-7975
  2025.6.0
• Updated libcurl version to version > 8.14
  APMDEV-7990
  2025.6.0
• Resolved issue that caused long loading times for transaction details,
  APMDEV-8003
  2025.6.0
• Resolved problem in the Analysis Server Cluster that resulted in no trace data.
  APMDEV-8016
  2025.6.0

APM Server 2025.3.0 (on-premise) - March 2025 Release

This release contains vulnerability updates and bug fixes, including:

• Update libcurl version to version > 8.12
  APMDEV-7838
  2025.3.0
• Update Apache Tomcat to v10.1.34 which addresses:
  • Missing content security policy header
  • Vulnerability BootStrap Version v.3.3.4
  • Turn off FormAuto Complete for HTML code
    APMDEV-7842
    2025.3.0
• Update OpenJDK 1.8.0_432 to address CVE-2025-21502
  APMDEV-7871
  2025.3.0
• Psockets unable to process large amounts of trace data in a timely manner and can affect instrumented application performance
  APMDEV-7841
  2025.3.0

APM Server 2024.10.1 (on-premise) - December 2024 Release

This release contains vulnerability updates that were inadvertently omitted from 2024.10.0.

• Update libcurl version to >=8.11.0 (CVE-2024-9681
  APMDEV-7823
  2024.10.1
• on-premise Application Server: OpenJDK 8 versions less than or equal to version 8u412 have been upgraded to address vulnerabilities
  APMDEV-7809
  2024.10.1
• Fix for missing source and destination values in the Web Request table
  APMDEV-7796
  2024.10.1
• Fix for missing database server names in appmap
  APMDEV-7790
  2024.10.1
• Updated libcurl versions less than 8.9.1 for vulnerabilities
  APMDEV-7773
  2024.10.1
• Fix for 403 Forbidden Error on APM WebUI when a search has a URL with an IP
  APMDEV-7771
  2024.10.1
• Upgraded PyCryptodome for versions less than 3.19.1 for Side Channel Leak vulnerability
  APMDEV-7761
  2024.10.1

APM Server 2024.10 (on-premise) - December 2024 Release

This release contains vulnerability updates and bug fixes, including:

• Update libcurl version to >=8.11.0 (CVE-2024-9681)
  APMDEV-7823
  2024.10
• on-premise Analysis Server: OpenJDK 8 versions less than or equal to version 8u412 have been upgraded to address vulnerabilities
  APMDEV-7809
  2024.10
• Fix for missing source and destination values in the Web Request table
  APMDEV-7796
  2024.10
• Fix for missing database server names in appmap
  APMDEV-7790
  2024.10
• Updated libcurl versions less than 8.9.1 for vulnerabilities
  APMDEV-7773
  2024.10
• Fix for 403 Forbidden Error on APM WebUI when a search has a URL with an IP
  APMDEV-7771
  2024.10
• Upgraded PyCryptodome for versions less than 3.19.1 for Side Channel Leak vulnerability
  APMDEV-7761
  2024.10

APM Server 2024.3 (on-premise) - May 2024 Release

The release includes support for Riverbed Operator. For more information on the Riverbed Operator, see https://github.com/riverbed/riverbed-operator

• Signature verification failing with self-signed certificates on Controller nodes
  APMDEV-7516
  2024.3
• Disk metrics not populated in Disk card
  APMDEV-7582
  2024.3
• Upgrade OpenJDK version <8u392 for on-premise APM Analysis Server​
  APMDEV-7588
  2024.3
• Update OpenSSH client to 9.6p1 or later (CVE-2023-48795)​
  APMDEV-7625
  2024.3
• Update libcurl version to >8.7 (CVE-2024-2398)
  APMDEV-7669
  2024.3
• on-premise Analysis Server support for RHEL 9
  APMDEV-7676
  2024.3

APM Server 2023.11.0 - December 2023 Release

This release contains the following bug fixes:

• Update ciphers to remove cbc ciphers
  APMDEV-7500
  2023.11.0
• Updated libcurl version from 7.29
  APMDEV-7489
  2023.11.0
• Updated the Analysis Server OpenJDK with 2023-10 release (8u391)
  APMDEV-7460
  2023.11.0
• Agent list page is taking more than 150s to load
  APMDEV-7440
  2023.11.0
• The Fixed Timeseries Operator not returning results
  APMDEV-6801
  2023.11.0
• The LRE's forwarding rule for port 80 leads customer security audit to fail
  APMDEV-6741
  2023.11.0

APM Server 2023.7.0 - November 2023 Release

This release contains the following bug fixes:

• Remove Password change page for read-only users (local and ldap users)
  APMDEV-7414
  2023.7.0
• ODB server crashes - Unexpected index segments overlap
  APMDEV-7386
  2023.7.0
• Negotiator not coming up online
  APMDEV-7291
  2023.7.0
• Dynamic alert email still attempting to send non-ascii characters in the body
  APMDEV-7276
  2023.7.0
• Harvest option disabled because of incorrect license calculation
  APMDEV-7256
  2023.7.0
• JSI Ajax code triggering a Chrome error logging nuisance: "Refused to get unsafe header"
  APMDEV-7247
  2023.7.0
• Fix for the WebUI no longer accessible after 2023.5 install on RHEL 8
  APMDEV-7244
  2023.7.0
• Fix to prevent spmap.sqlite-wal file reaching 250GB+
  APMDEV-7182
  2023.7.0
• Analysis Server updated to openJDK with 2023-04 security release
  APMDEV-7164
  2023.7.0
• Fix for showing processes in an instrumented status and their harvest option disabled
  APMDEV-7152
  2023.7.0

APM Server 2023.5.0 - May 2023 Release

This release contains the following enhancements:

• Red Hat Enterprise Linux 8 (RHEL 8) is now supported by APM Server

Additionally, this release contains bug fixes:

• Agent License: No license but trace data still being harvested
  APMDEV-7160
  2023.5.0
• Fixed for the false triggering of dynamic alerts
  APMDEV-7090
  2023.5.0
• Fix for the silo_query, which could exhaust memory under some conditions
  APMDEV-7087
  2023.5.0
• Fixed Timeseries Operator, not returning results
  APMDEV-6801
  2023.5.0

APM Server 2022.11.1 - March 2023 Release

This release contains the following enhancements:

• OpenTelemetry support for on-premise environments (learn more).
• Secure Agent mode (learn more).
• New landing page (learn more).

Additionally, this release contains bug fixes:

• Fix for the silo_dispatch on the cluster's controller, which was crashing after an upgrade to 2022.11.0.49
  APMDEV-6982
  2022.11.1
• Fixing Analysis Server upgrades to include upgrading the Java version
  APMDEV-6958
  2022.11.1
• The Analysis Server should return 0 rather than NA for exception_count if there are no exceptions
  APMDEV-6728
  2022.11.1

APM Server 2022.11 - February 2023 Release

This release does not contain new features, but provides bug fixes.

• Updated Java version to OpenJDK 8<=352 (Nessus Plugin ID 170536)
  APMDEV-6837
  2022.11
• Updated bad browser message to reflect IE11 being EOL (end-of-life)
  APMDEV-6813
  2022.11
• Dynamic Alerts Email does not properly encode Subject when non-ascii characters are present
  APMDEV-6811
  2022.11
• Time series operator not returning results
  APMDEV-6801
  2022.11
• A fix has been applied to populate the server tags field in classic alerts
  APMDEV-6766
  2022.11
• Java CVE security updates were applied to on-premise Analysis Server
  APMDEV-6762
  2022.11
• Added cleared status to SNMP trap events
  APMDEV-6712
  2022.11
• Fix for issue where Custom Metrics aggregation was unable to keep up with incoming data, which caused journal files to fill the disk
  APMDEV-6696
  2022.11
• Fixed Journal files in /mnt/data/silo/data/journal/app2 modified, so they are no longer world writable
  APMDEV-6679
  2022.11
• Analysis Server fix where some customer transaction data was not being processed
  APMDEV-6652
  2022.11
• Modified WebUI Implementations for Secure Agent mode
  APMDEV-6589
  2022.11
• Applied Analysis Server 2022.3 vulnerability (CVE-2022-23181)
  APMDEV-6395
  2022.11
• Applied security vulnerability fix for missing HSTS from HTTPS Server
  APMDEV-4850
  2022.11
• Applied security update to prevent customer scanners from flagging sshd accepts kex algorithm
  APMDEV-4255
  2022.11

APM Server 2022.5 - July 2022 Release (on-premise)

This release does not contain new features, but provides bug fixes.

• Analysis Server stopped harvesting data after upgrade due to missing controller.crt
  APMDEV-6340
  2022.5
• Transaction detail page missing exceptions/call tree
  APMDEV-6320
  2022.5

APM Server 2022.3 - March 2022 Release (SaaS and on-premise)

This release does not contain new features, but provides bug fixes.

• JSI v1407 could cause errors in web pages
  APMDEV-6078
  2022.3
• Ensure all sensitive/confidential and important cookies such as session ID cookies to be marked as HttpOnly
  APMDEV-6030
  2022.3
• Ensure all Cookies not set secure in SSL/TLS sessions are marked secure
  APMDEV-6029
  2022.3
• Vulnerable D3 JS library - Upgraded to the latest secure version
  APMDEV-6028
  2022.3
• WMI config change is not always persisting
  APMDEV-6015
  2022.3
• Fixed OpenJDK 1.8.0_302 Vulnerabilities
  APMDEV-5998
  2022.3
• Install Agents page - AIX / Solaris installs removed from download list
  APMDEV-5962
  2022.3
• Added WebHooks to current AS Alerting mechanism
  APMDEV-5826
  2022.3
• The Statistics Operator may not show results for a 24 hour time range
  APMDEV-5704
  2022.3
• Fixed Nginx Security Vulnerability - Nginx 0.6.x < 1.20.1 1-Byte Memory Overwrite RCE (CVE-2021-23017)
  APMDEV-5670
  2022.3
• Agents do not remain connected to cluster due to websocket timeout
  APMDEV-5657
  2022.3
• Calls operator not always displaying data for sql statements
  APMDEV-5615
  2022.3
• Stitching processing seems slow
  APMDEV-5604
  2022.3
• Fixed Apache Tomcat 9.0.41 vulnerabilities (CVE-2021-25122;CVE-2020- 9484)
  APMDEV-5574
  2022.3
• Sorting by Web Request method in transaction detail sometimes throws an error
  APMDEV-4797
  2022.3
• Sort by Service Time column in transaction detail for Web Request is not working as expected
  APMDEV-4796
  2022.3

APM Server 2021.6 - September 2021 Release (SaaS and on-premise)

This release does not contain new features, but provides bug fixes.

• Updated Nginx
  APMDEV-5585
  2021.6
• A small number of transactions are occasionally shown with a future date
  APMDEV-5532
  2021.6

APM Server 11.8.4.6 - June 2021 Release

This release does not contain new features, but provides bug fixes.

• Vulnerable java-1.8.0-openjdk-1.8.0.272 on APM AS 11.8.2
  APMDEV-5502
  11.8.4.6

APM Server 11.8.2 - April 2021 Release

This release does not contain new features, but provides bug fixes.

• Analysis Server stops processing data due to deadlock
  APMDEV-5297
  11.8.2
• Ensure Nginx version is 1.18 or later
  APMDEV-5259
  11.8.2
• Unknown error when opening Txn detail -ValueError: invalid literal for int() with base 10
  APMDEV-4927
  11.8.2
• Unable to open Txn details for larger trace
  APMDEV-4892
  11.8.2
• Unable to configure SAML - SAML Authentication Error Signature validation failed
  APMDEV-4291
  11.8.2

APM Server 11.8.0 - January 2021 Release

This release does not contain new features, but provides bug fixes.
This release is a maintenance release only and it does not contain new features, but provides bug fixes.

• java.lang.StringIndexOutOfBoundsException in AgentRT Process Collector
  APMDEV-4949
  11.8.0
• WMI metrics are not available due to locale
  APMDEV-4924
  11.8.0
• Update OpenJDK version from 1.8.0_262 to 1.8.0_271
  APMDEV-4863
  11.8.0
• Custom metrics screen shows HTTP error 400 and not loading
  APMDEV-4484
  11.8.0

APM Server 11.7.1 - September 2020 Release

This release does not contain new features, but provides bug fixes.

Limitations in this release:

• The minimum supported version of .NET Framework for the Agent11.7 is .NET Framework 4.6.1
• To instrument earlier versions of .NET Framework, please use 10.21.x LTS agent builds.
• .NET Core 2.0 and later continue to be supported with 11.7

Resolved Issues in this release:

• Tag support in process and service metrics
  APMDEV-4763
  11.7.1
• TypeAhead search in Custom Dashboards for service state does not work
  APMDEV-4756
  11.7.1
• nginx-external fails to start after upgrading OVA
  APMDEV-4712
  11.7.1
• 500 The call failed on server error on Txn detail page
  APMDEV-4663
  11.7.1
• When editing dashboard, adding a custom card pane sometimes keeps loading forever.
  APMDEV-4656
  11.7.1
• AS ProfilerSockets: deleted files resulting in file handles hanging around
  APMDEV-4611
  11.7.1
• AS ProfilerSockets-Client protocol results in many connections in TIME_WAIT_STATE
  APMDEV-4610
  11.7.1
• AS ProfilerSockets: open files/sockets are not closed when client terminates
  APMDEV-4609
  11.7.1
• Portal building APM URL with server.tag which does not exist anymore with APM 11.5
  APMDEV-4575
  11.7.1
• Custom metrics screen shows HTTP error 400 and not loading
  APMDEV-4484
  11.7.1

APM Server 11.6.0 - 5 August 2020 Release

This release does not contain new features, but provides bug fixes.

Resolved Issues in this release:

• Silo child processes unable to start after upgrade to 11.4.3
  APMDEV-4554
  11.6.0
• WebRequest REGEX based TAGS not working with Cookies
  APMDEV-4526
  11.6.0
• Silo dispatch crashes in rare race condition
  APMDEV-4500
  11.6.0
• signed certs should not be required if cert validation is disabled
  APMDEV-4493
  11.6.0
• Most Analysis Operators fail with error when using WebRequests instead of txn segments and E2E txn
  APMDEV-4476
  11.6.0
• WebRequest method mismatch between search and txn detail pages
  APMDEV-4465
  11.6.0
• Web Requests export fails on 11.5.0
  APMDEV-4463
  11.6.0
• Transaction detail screen fails to load
  APMDEV-4442
  11.6.0
• SSH Server Public Key Too Small - ssh-dss1024 bits
  APMDEV-4320
  11.6.0
• HTTP OPTIONS Method Enabled on Analysis Server
  APMDEV-4262
  11.6.0
• Support for agentless instrumentation in PCF
  APMDEV-4194
  11.6.0
• Multiple Inbound URL's being stitched together (Overstitching)
  APMDEV-4099
  11.6.0

Known Issues in this release:

• AS ProfilerSockets: deleted files resulting in file handles hanging around
  APMDEV-4611
• AS ProfilerSockets-Client protocol results in many connections in TIME_WAIT_STATE
  APMDEV-4610
• AS ProfilerSockets: open files/sockets are not closed when client terminates
  APMDEV-4609

APM Server 11.4.3 - April 2020 Release

This release does not contain new features, but provides bug fixes.

Note

Installing Agents on AIX, Solaris, SUSE Linux, Windows Server 2008 R2SP1 64-bit, as well as systems with Java versions prior to Version 6 is no longer supported for Version 11 Agents. However, they are still supported for Version 10 Agents on Version 11 Analysis Servers.

Original source

This document provides a comprehensive table of feature enhancements, organized by version (including release state) and feature description.

The Aternity Module (formerly known as Aternity Agent ) monitors end user experience by measuring device and application performance. It is a seamless background utility which runs on each monitored device, and reports its data to Aternity.

What's New in Aternity Module 26.3 (RC)

This Aternity Module release offers the following enhancements:

• New out-of-the-box Citrix monitoring package, including a set of new data collections and supporting Troubleshoot Device dashboard tab.
  • New Citrix Static Attributes Collection, including:
    • Desktop groups (registry oriented)
    • Catalog Name (the deployed image)
    • Hypervisor Name
    • Desktop Kind (private or shared)
  • New Citrix Monitored Attributes Collection, including:
    • ICA RTT
    • HDX Encode Time
    • Thinwire I/O Average FPS
  • Session Logon Measurement and Breakdown
  • These metrics are also available in the Advanced Dashboard and through the REST API
• OS Arch detection (Added Arm64)
• Security and performance enhancements

What's New in Aternity Module 25.7 (GA)

Released for General Availability in September 2025

This Aternity Module release offers the following enhancements:

• New out of the box HRC monitoring for GPU, NPU, CPU Thermal and throttling, providing a more comprehensive view of system performance.
• New option to enable Location Services. This has been added to address recent Microsoft policy changes that can otherwise disable Wi-Fi monitoring. Learn more
• Support for monitoring BSOD (Blue and Black) in Win11 24H2
• Support for TLS 1.3 (requires operating system support for TLS 1.3)
• Security and performance enhancements.

What's New in Aternity Module 25.1 (GA)

Released for General Availability in June 2025

The new Aternity Module offers the following enhancements:

• Support for Monitoring JDK 8-23 based applications
• Performance Improvements
• Security fixes and enhancements
• Support for Windows Server 2025

This release includes all resolved issues from previous releases.

What's New in Aternity Module 24.9 (GA)

Released for General Availability in February 2025

The Aternity Module offers the following enhancements:

• Support for Intel Module for WiFi and Thunderbolt monitoring ( read here how to deploy the module )
  Learn more about WiFi and Thunderbolt monitoring.
• Security and performance enhancements

This release includes all resolved issues from previous releases.

What's New in Aternity Module 12.2.5 (GA)

Released for General Availability in October 2024

This release contains the following enhancements:

Aternity Module should be deployed and managed from the Riverbed Unified Agent.

Application monitoring

Aternity Module automatically detects and monitors all processes used by an application by its root process. Users are not required anymore to add each process separately as a managed application, but only the root parent process (used to launch the application). Aternity will accumulate all of the resource consumption and Desktop usage time into the root process, i.e. the application.

Simplifying business activities creation

With multi-processes structured applications, now there is no need to specify all of the processes while recording in a manual mode with the Aternity Recorder.

MS New Outlook as a managed application

Out of the box, Aternity Module supports monitoring MS New Outlook, including Process Resource Consumption.

MS New Outlook OOTB business activities

Aternity now monitors predefined activities out of the box for the New Outlook. Learn more.

ServiceNow web application monitoring

It is possible now to use WAC to create custom activities for monitoring ServiceNow web application.

Support for AppX and MSIX package formats

Aternity Module now reports Installed applications also for AppX and MSIX formats (Windows Store based and others). What is MSIX? Learn here.

Deploying the Upgrade

Important

Unified Agent is the only way to deploy and distribute the Aternity Module.

The Riverbed Unified Agent is a versatile container component designed to simplify the deployment, upgrade, and management of Riverbed modules (formerly called as agents) for our valued customers. With the Unified Agent, you can conveniently deploy different modules (for Windows, Mac, or Linux devices) directly from within the UI, streamlining your workflow and enhancing efficiency.

First, read carefully about software system requirements.

Then, learn how to install the Unified Agent and its module.

Release States

This section lists different states of the release cycle. The state reflects the stability level of the module only, and not related to functionality. When the module changes its state (for example, from CA to GA), its functionality remains the same.

• Release Candidate (RC) – This is a new version which Riverbed intends to make available for customers in the near future. You may deploy it to a handful of endpoints to try its features.
• Controlled Availability (CA) – This is a production-ready, supported module with which you may start a limited scale rollout to your organization.
• General Availability (GA) – This is a default module available for full scale deployment to all environments.

Original source