General Main Release 10.1.0 CU22 – Preview

Important

We are still working on this release. Some release notes may still be modified or moved to a later release. Check back soon for updates!

Tip

For information on how to upgrade DataMiner, see Upgrading a DataMiner Agent.

Enhancements

Elasticsearch: Sending a GetInfoMessage of type 'IndexingConfiguration' with an invalid DataMiner ID will now only return the Elasticsearch configuration of the local DMA [ID 34774]

When a GetInfoMessage of type "IndexingConfiguration" was sent containing an invalid DataMiner ID, up to now, the Elasticsearch configuration of all DMAs would be returned.

From now on, when the DataMiner ID in a GetInfoMessage request of type "IndexingConfiguration" is invalid, only the Elasticsearch configuration of the local DMA will be returned instead.

DataMiner upgrade: Enhanced method to delete locked files [ID 34779]

When, during a DataMiner upgrade, an attempt was made to delete files that were locked by certain processes, up to now, that attempt would fail, causing those files to remain on the system until the next upgrade.

From now on, when an attempt to delete a file during a DataMiner upgrade fails, the extension of that file will be replaced by .SLReplace and, later on in the upgrade process, the file will then be deleted by SLHelper.

DataMiner Cube: Stream Viewer enhancements [ID 34837] [ID 34838]

The Stream Viewer tree view now supports more levels. This will allow you to display more detailed information.

For example, in case of HTTP communication, there will now be extra levels for sessions, connections, requests/responses, parameters*, and even status codes and error codes.

*only in case of a response

DataMiner Cube - Visual Overview: Enhanced performance when loading a visual overview that contains a large number of shapes linked to EPM objects [ID 34874]

Because of a number of enhancements, overall performance has increased when loading a visual overview that contains a large number of shapes linked to EPM objects.

DataMiner Cube - Settings: 'Show the DataMiner TV section' setting has been removed [ID 34877]

The Show the DataMiner TV section setting has been removed from the User > Cube section of the Settings window.

Element errors and notices will now be closed as soon as the element in question is stopped [ID 34927]

The following element errors/notices generated by SLDataMiner will now automatically be closed when the elements in question are stopped.

Creating log-factory for <x> failed.
Creating the log-file for <x> failed.
Initialize xml for <x> failed.
Parsing the settings for <x> failed.
Creating element-object for <x> failed with <y>.
Initializing the element <x> failed.
Starting the element <x> failed.
Starting the element <x> failed. No element object.
Creating Database tables for <x> failed.
Creating element-objects for <x> failed.
Initializing the communication <p> for <x> port failed. / Initializing the communication of port <p> for <x> failed.
Initializing the protocol for <x> failed.
Initializing the element for <x> failed.
Starting the protocol for <x> failed.
Starting the protocol for <x> failed. No Protocol object.
Starting the derived element for <x> failed.
Starting the element <x> failed. No element object.
Creating element-object for <x> failed with <y>.

DataMiner Cube - Trending: Trend points with value "0" will now also be exported to CSV [ID 35124]

Up to now, when you exported real-time trend data to a CSV file, trend points with value "0" would not be included. From now on, those values will be exported as well.

Fixes

'One or more of the following modules are not licensed' error would incorrectly not list the unlicensed modules [ID 34407]

When a required software license cannot be found, a One or more of the following modules are not licensed: ... message will appear.

In some cases, instead of listing the unlicensed modules, this message would incorrectly only mention "None".

Dashboards app - Time range feed: Quick pick buttons would not be displayed in the correct order [ID 34759]

When a time range feed was configured to show quick pick buttons, those buttons would not be displayed in the correct order. From now on, quick pick buttons will be displayed in chronological order.

Standalone parameters belonging to another child of the same DVE parent element could be set to 'Not Initialized' when a row linked to a DVE child element was deleted [ID 34785]

When a row linked to a DVE child element was deleted, in some cases, standalone parameters belonging to another child of the same DVE parent element could be set to "Not Initialized".

DataMiner Cube - Alarm Console: Alarm tab of type 'Active alarms linked to cards' would incorrectly not show any alarms when you opened a function card [ID 34799]

When the Alarm Console had an alarm tab of type Active alarms linked to cards, that tab would incorrectly not show any alarms when you opened a function card, even when that function had active alarms.

Also, when you added a new alarm tab, clicked Apply filters, and added an element filter, then you would incorrectly also be able to select virtual functions from the list of elements. From now on, only when you add a function filter will you be able to select virtual functions from the list of functions.

Memory leak in SLDataGateway during a Cassandra Cluster migration [ID 34829]

During a Cassandra Cluster migration, SLDataGateway would leak memory due to paging handlers not being cleaned up correctly.

DataMiner Cube - Visual Overview: Preset specified in a Spectrum Analysis component would incorrectly not be loaded [ID 34833]

When you had specified a preset in a shape that contained a Spectrum Analysis component, the preset would incorrectly not be loaded when you opened the visual overview in Cube.

Problem with SLElement when a description.xml file was updated while an alarm was being unmasked [ID 34860]

In some cases, an error could occur in SLElement when a description.xml file was updated while an alarm was being unmasked.

HTTP requests would incorrectly not be retried when WinHTTP threw a SEC_E_BUFFER_TOO_SMALL error [ID 34888]

When an HTTP request is sent, in some cases, WinHTTP can incorrectly throw a SEC_E_BUFFER_TOO_SMALL error when the server is using TLS 1.2.

From now on, when this error is thrown, DataMiner will retry the HTTP request the number of times specified for the HTTP connection in question.

SLLogCollector would become unresponsive after executing a nodetool command [ID 34909]

When the JAVA_HOME variable was not set, SLLogCollector would become unresponsive after executing a nodetool command.

From now on, when SLLogCollector times out after executing a nodetool command, it will log a timeout message in its log file and proceed.

SLDataGateway was not always able to parse the result of a 'nodetool status' command [ID 34929]

The SLDataGateway process periodically checks the status of the local Cassandra node by executing a nodetool status command and parsing the result. When Cassandra was still starting up, some values in the output could not always be parsed, leading to SLDataGateway incorrectly marking the database as unavailable.

DataMiner Cube - EPM: Problem with topology filter [ID 34931]

When you opened a topology chain and selected a field in the topology filter, in some cases, the fields above the one you selected would incorrectly not get selected automatically.

Problem with SLProtocol when trying to update a parameter of type 'read bit' [ID 34935]

In some cases, an error could occur in SLProtocol when trying to update a parameter of type read bit.

DataMiner Cube - Visual Overview: Trend graph would incorrectly show 'No data' [ID 34955]

When a visual overview on an EPM card contained a trend graph, in some cases, that graph would incorrectly show No data while its legend would show the correct data.

Elements would not show up in client applications due to an incorrect credential library GUID stored in their Element.xml file [ID 34956]

In some cases, an incorrect credential library GUID could get stored in the Element.xml file of certain elements. As a result, although they were active and working as expected, those elements would not get loaded into SLNet and would not show up in client applications such as DataMiner Cube.

Web apps - Line chart component: Chart would incorrectly display non-existing data when the time window included a period in the future [ID 34959]

When the time window of a line chart component showing trend data included a period in the future, the chart would incorrectly display non-existing data for that period in the future. From now on, the chart will stop at the current time.

Dashboards app & Low-Code Apps: Problem with 'Number of columns' input box [ID 34966]

When you were editing a dashboard or a low-code app, and the edit side panel was very narrow, in some cases, the Number of columns input box on the Settings tab could not be used as it would only be partly visible.

Also, in some cases, the value in the Number of columns input box could incorrectly not be reset to the factory default.

DataMiner Cube: Problem when opening scheduled tasks, Automation scripts or Correlation rules containing actions that include PDF reports [ID 34997]

When, in Scheduler, Automation or Correlation, you opened scheduled tasks, Automation scripts or Correlation rules containing actions that include PDF reports, in some rare cases, the data linked to those reports (i.e. the elements and services in view selection) could not be loaded. This data will now be loaded correctly. Also, a "Loading" indicator will now be displayed and the actions will remain disabled while the data is being loaded. When an error occurs while loading the protocols associated with said data, a clear warning entry will also be added to the Cube logging.

Note

From now on, in the Elements and services in view selection list, it will also be possible to select parameters of enhanced services.

DataMiner Cube - Spectrum Analysis: Selected measurement point no longer selected after playing a spectrum recording [ID 35001]

When you selected a measurement point of a spectrum trace, and then played a spectrum recording in which other measurement points were used, the measurement point you selected would incorrectly no longer be selected when the spectrum recording stopped playing.

DataMiner Cube - Alarm Console: Cube freezes when loading a large sliding window [ID 35032]

When you opened an alarm tab of type "sliding window" with a large number of alarm trees, in some cases, the UI could become unresponsive.

DataMiner Cube: Y-axis values could be missing when opening a trend graph [ID 35060]

When you opened the trend graph of a parameter that contained discrete values or exceptions, in some cases, Y-axis values could be missing.

DataMiner Cube - Trending: Trend graph would start to flicker when its data was updated [ID 35181]

When you opened a trend graph and left it open for a while, it would start to flicker when its data was updated.