Release Note for Aternity on-premise 12.2

Version 12.2 of Aternity on-premise is a minor release that provides security enhancements, new versions for Tableau and Vertica, and the ability to configure advanced collection.

This article covers the following sections:

Deploy Aternity on-premise 12.2

Aternity 12.2 resolves several known issues. You can deploy a clean setup of Aternity on-premise 12.2 or update from earlier versions.

For the new features in Aternity on-premise 12.2 release, learn here.

Resolved Issues

Description Issues ID Salesforce ID

Links embedded in on-premise 12.1 Product Tours lead to version 12.0 articles.

You can manually select 12.1 from the drop down. This is not necessary because the content is correct.

DEM-5510

NA

In the Agent Administration screen, the version column sorting does not work as expected and does not display the versions in the numeric order.

DE23890

NA

Known Issues

Description Issue ID In Version

Redirect link from NetProfiler may fail to redirect to the correct device.

DEM-10198

12.2

Measurements with undefined status handled incorrectly in several dashboards. Status of a score might be colored wrong in User Experience, Monitor Application, and Commonalities Analysis.

DEM-9774

12.2

A simple dashboard saved before the update cannot be found after the update.

DEM-9627

12.2

(Advanced Custom Data): When a saved dashboard is loaded in the Edit mode, all measurements and contextuals are listed, including the irrelevant ones. Also, the Legends disappear.

DEM-9283

12.2

Tableau log cleaning does not run automatically so that on-premise Aternity Dashboard Gateway Server does not have any automatic log cleaning, resulting in logs building up and filling available disk space.

Clean up log files manually from time to time. Run
tsm maintenance cleanup -l --log-files-retention <number of days>

You can add a scheduled task to run this command periodically.

DEM-3803

12.2

In Chrome, when as administrator of Aternity you go to the Advanced Tools > Backup and Restore section and download the backup file of the saved dashboards, the session may expire and return you to the login screen.

Note that the file properly downloads, and in case the session unexpectedly expires, login to Aternity again.

DE23932

12.2

IdP metadata update sometimes takes few hours or requires a restart in order to work with the new configuration.

DE23825

12.2

There is a limitation to configure SAML on a SSL secured system when full hierarchy keystore (JKS) is in use. The limitation is that expected entry of type PrivateKeyEntry cannot be automatically selected from list of the keys in keystore.

Workaround: Refer to the details in this article.

DE23868

12.2

In the saved dashboards, no data will be shown until you manually remove the automatically added Month filter.

Workaround: Create a custom calculated Month field in the following way: Month - left(str(DATETRUNC('month',[Timeframe])),3) + left( right(str(DATETRUNC('year',[Timeframe])),13),5)

DE23828

12.2

Running a lot of docker containers may cause high memory consumption of Linux NetworkManager.

To resolve, Aternity recommends disabling NetworkManager service on the Docker Components machine (run as a privileged OS user systemctl mask NetworkManager).

N/A

12.2

After a fresh installation, if no Agents have been connected within 4 hours, Vertica Scheduler may enter the Failing state. As soon as Agents are connected and data starts flowing to Vertica Database Server, the issue gets resolved.

N/A

12.2

The Aternity Docker Components Server stores truststore and keystore passwords in clear text in the container definitions for those containers that can be configured with ssl.

N/A

12.2