General Main Release 10.2.0 CU14
Note
For known issues with this version, refer to Known issues.
Tip
For information on how to upgrade DataMiner, see Upgrading a DataMiner Agent.
Enhancements
DataMiner upgrade will not be performed if NATS is not installed and running [ID 33304]
When you launch a DataMiner upgrade, from now on, the upgrade process will not be allowed to start if NATS is not installed and running.
Note
This check will be skipped if the current DataMiner version is older than version 10.1.0.
DataMiner Cube: Database TTL settings will now be limited to 10 years [ID 35533]
From now on, DataMiner Cube will no longer accept database TTL settings that exceed 10 years.
Security enhancements [ID 35668]
A number of security enhancements have been made.
Alarms generated when a database goes in offload mode will now have severity 'Notice' instead of 'Critical' [ID 35749]
When a database went in offload mode, up to now, an alarm with severity Critical was generated. From now on, an alarm of severity Notice will be generated instead.
Monitoring app: Elements, services and views opened by clicking a Visio shape will open in the same tab instead of a new tab [ID 35781]
In the Monitoring app, from now on, elements, services and views opened by clicking a Visio shape will open in the same tab instead of a new tab.
GQI data sources that require an Elasticsearch database will now use GetInfoMessage(InfoType.Database) to check whether Elasticsearch is available [ID 35907]
Up to now, GQI data sources that require an Elasticsearch database used the DatabaseStateRequest<ElasticsearchState> message to check whether Elasticsearch was available. From now on, they will use the GetInfoMessage(InfoType.Database) message instead.
Web apps: Enhanced error handling when executing an interactive Automation script by clicking a DOM button [ID 35909]
Overall error handling has been improved when executing an interactive Automation script by clicking a DOM button in a web app.
DataMiner Cube - Alarm templates: 'Condition (Monitoring disabled if condition is true)' column renamed to 'Condition (Parameter excluded if condition is true)' [ID 36007]
When you were editing an alarm template, one of the many columns on the screen was named Condition (Monitoring disabled if condition is true). This column has now been renamed to Condition (Parameter excluded if condition is true).
Fixes
SLLogCollector: Problem when collecting multiple memory dumps with the 'Now and when memory increases with X Mb' option [ID 35617]
When the SLLogCollector tool had to collect memory dumps of multiple processes with the Now and when memory increases with X Mb option, it would incorrectly only collect the memory dump of the first process that reached the specified Mb limit.
From now on, it will collect at least the "now" dump for each of the selected processes.
NATS would incorrectly be re-installed when a WMI query error occurred while the NATS installer was being run at DMA startup [ID 35647]
When the NATS installer was being run at DMA startup, in some cases, due to an issue with a WMI query, NATS could incorrectly be re-installed, even though NATS and NAS were already running.
From now on, the execution of the NATS installer at DMA startup will be skipped when NATS is already running. Also, if an error occurs when running a WMI query during the execution of the NATS installer, a message saying that the re-installation has failed will be added to the SLUMSEndpointManager.txt log file.
Note
When an error occurs while running a WMI query, and no NATS/NAS service is running, NATS will not be installed automatically. A manual installation of NATS will be needed.
Existing masked alarms would incorrectly affect the overall alarm severity of an element [ID 35678]
Existing masked alarms would incorrectly affect the overall alarm severity of an element.
Dashboards app: Sticky component menus would no longer be fully visible after you had changed the number of dashboard columns [ID 35702]
Sticky component menus would no longer be fully visible after you had changed the number of dashboard columns.
Failover: Offline agent would incorrectly try to take a backup of the Elasticsearch database [ID 35721]
When, in Failover setups, you configure a DataMiner backup on the online agent, the same backup will also be scheduled on the offline agent, and if these setups have a clustered Elasticsearch database, a backup of that database cluster will be included in the DataMiner backup.
In Failover setups where both agents included a local Elasticsearch database that was part of an Elasticsearch cluster, the online agent would fail to take a backup of the Elasticsearch databases due to a backup in progress, triggered earlier by the offline agent.
From now on, only the online agent will be allowed to take a backup of the Elasticsearch database, and the offline agent will log the following entry:
Elastic backup will not be taken - Only active agents from a failover pair can take the backup.
SLElement could leak memory when updating alarm templates containing conditions [ID 35728]
In some cases, SLElement could leak memory when updating alarm templates containing conditions.
Memory leak in SLAnalytics [ID 35758]
In some cases, SLAnalytics kept on waiting on a database call, which eventually led to the process leaking memory.
SLProtocol would interpret signed numbers incorrectly [ID 35796]
SLProtocol would interpret signed numbers incorrectly, causing parameters to display incorrect values.
Dashboards app & Low-Code Apps: Duplicated component would not have the size as the original [ID 35804]
When you duplicated a component, the size of the duplicate would incorrectly be limited to 30 rows. From now on, when you duplicate a component, the duplicate will have the same size as the original.
Dashboards app: A table component could appear to be empty when you rapidly switched between visualizations [ID 35831]
In some cases, a table component could appear to be empty when you rapidly switched between visualizations.
Also, an error could be thrown when you tried to add an invalid query to a component.
DataMiner Maps: Markers could disappear when a layer was enabled or disabled [ID 35838]
In some cases, markers could disappear when a layer was enabled or disabled.
DataMiner Cube - Alarm Console: It could take a long time for an active alarms tab to load on a system with a large number of masked alarms [ID 35843]
Due to a caching issue, on a system with a large number of masked alarms, it could take a long time for an active alarms tab to load.
DataMiner Cube - Alarm Console: Base alarm updates would not be shown when the active alarms tab was filtered [ID 35845]
In a filtered active alarms tab, in some cases, a base alarm will match the filter while the correlated alarm will not. In that case, the base alarm will be shown while the correlated alarm will not.
However, up to now, when a base alarm was updated, the update would not be reflected in the Alarm Console until the filter was removed.
Business Intelligence: At SLA startup, the active alarms would no longer be in sync with the actual alarms affecting the SLA [ID 35862]
At SLA startup, in some cases, the active alarms would no longer be in sync with the actual alarms affecting the SLA.
Also, a number of other minor fixes with regard to SLA management have been implemented.
Problem when an SLA element was stopped or deleted while a parameter that triggered a QAction of the SLA in question was being updated [ID 35892]
An error could occur when an SLA element was stopped or deleted while a parameter that triggered a QAction of the SLA in question was being updated.
Dashboards app & Low-Code Apps - GQI components: Problems when a GQI request failed [ID 35904]
When a GQI request failed, some GQI components would show either an unrelated error or no error at all, while other GQI components would show a correct error but incorrect data.
Dashboards app & Low-Code Apps: Performance could decrease when State components had their Design option set to 'Auto size' [ID 35905]
Up to now, overall performance of a dashboard or a low-code app could decrease when it contained State components of which the Design option was set to "Auto size". A number of enhancements have now been made to prevent performance from decreasing in this case.
Web apps: Login button would incorrectly be disabled on Edge and Chrome [ID 35906]
Up to now, in some cases, the login button would incorrectly be disabled when you opened a web app in Microsoft Edge or Google Chrome.
Monitoring app - Visual Overview: Clicking a region that opened an element, service or view card would incorrectly cause the Monitoring app to reload [ID 35908]
When, in the Monitoring app, you clicked a region in a visual overview that opened an element, service or view card, up to now, the entire Monitoring app would reload. From now on, when you click a region in a visual overview that opens an element, service or view card, the card in question will open but the Monitoring app will no longer be reloaded.
Dashboards app & Low-Code Apps - Clock components: Clock time would not update when set to server time [ID 35912]
When a clock component (analog or digital) was set to use server time, the clock time would not update.
DataMiner Cube - Visual Overview: [ServiceDefinitionFilter] placeholder would incorrectly not be resolved when used in a table row filter [ID 35923]
When, in a shape data field of type ParameterControlOptions, you had specified a table row filter that included a [ServiceDefinitionFilter] placeholder (e.g. "TableRowFilter:101=[ServiceDefinitionFilter]"), that placeholder would incorrectly not be resolved, causing the linked table control to be empty when filtered.
DataMiner Cube - Spectrum analysis: Problem when opening a spectrum element with an empty username [ID 35927]
An error could occur when you tried to open a spectrum element of which the username was set to NULL.
Also, an exception could be thrown when you tried to copy spectrum settings to the Windows clipboard.
SNMP: OIDs with a leading dot would incorrectly no longer be allowed [ID 35954]
OIDs with a leading dot would incorrectly no longer be allowed. From now on, OIDs with a leading dot are allowed again.
DataMiner Cube - Surveyor: Dragging multiple items from a view card onto a view in the Surveyor did not work as expected [ID 35955]
Dragging several elements or services from a view card onto a view in the Surveyor did not work as expected.
From now on, when you drag several elements or services from a view card onto a view in the Surveyor
- the items in that view will be moved to the view in Surveyor, and
- the items in any of its sub-views will be copied to the view in the Surveyor.
If you want to the items in the view to be copied to the view in the Surveyor instead of moved, keep the Ctrl key pressed while dragging them.
Low-Code Apps: Page names and panel names could incorrectly be empty [ID 35960]
Up to now, page names and panel names could incorrectly be empty. From now on, this will no longer be allowed.
NT Notify type NT_GET_BITRATE_DELTA would not return a valid value for a table with a single row [ID 35967]
In some rare cases, NT Notify type NT_GET_BITRATE_DELTA (269), which retrieves the time between two consecutive executions of the specified SNMP group (in ms), would not return a valid value for a table with a single row.
Dashboards app - Line & area chart: Legend would show an incorrect number of disabled parameters [ID 35970]
When configuring a line & area chart, you can use the Chart limit setting to specify the maximum number of parameters that can be displayed in the chart. The excess parameters will then be disabled but remain available in the chart legend, so that they can be enabled again manually.
In some cases, the number of disabled parameters shown in the legend would be incorrect.
'SLA Affecting' property of cleared or re-opened alarm would incorrectly contain 'Y' instead of 'Yes' [ID 35987]
When an alarm was cleared and re-opened for the same parameter or parameter key combination, its SLA Affecting property would incorrectly contain "Y" instead of "Yes".
Dashboards app & Low-Code Apps: Filter box of visualizations panel would not reset [ID 36000]
When you reloaded the editor, by clicking the Refresh button while editing a dashboard or by switching pages while editing a low-code app, or when you switched to edit mode after previewing or publishing a low-code app, the filter box of the visualizations panel would incorrectly not be reset.