Table of Contents

DataMiner Cube Feature Release 10.5.6

Note

For known issues with this version, refer to Known issues.

Tip

Highlights

New features

View cards: New 'Isolation mode' column in element list [ID 42562]

In view cards, the element list now has a new Isolation mode column, which displays the isolation mode of each element in the list.

By default, this column will be hidden. To add this column to the list, right-click a column header, and select Add/Remove setting column > Isolation Mode.

These are the possible values that can be displayed in the Isolation mode column:

Value Description
None Not applicable. E.g. When viewing the All page of a service.
Disabled The element is not running in isolation mode.
Enabled (protocol) The element is running in isolation mode because of a setting configured in the protocol.xml file, which applies to all elements that are using this protocol version.
Enabled (element) The element is running in isolation mode because of a setting configured in the element itself.
Enabled (DMA) The element is running in isolation mode because of a setting configured on DMA level, which applied to all elements that are using this protocol.

Changes

Enhancements

Trending: SPI log entry containing the loading times of the trend graph labels will be added to SLClient.txt [ID 42514]

When you open a trend graph, from now on, an SPI entry containing the loading times of the trend graph labels (including metadata like loaded trend data points, etc.) will be added to the SLClient.txt log file.

In the Augmented Operations alarm settings window, which you can access in the alarm template editor by clicking the button in the Analytics or Anomalies column for a given parameter, you can now find a link to the RAD Manager app.

If already installed on your system, the app will open. If not, you will be referred to the RAD Manager page in the Catalog.

Note

This link will only be available if the DataMiner server uses DataMiner 10.5.4/10.6.0 or higher.

DataMiner Cube desktop app: Enhanced behavior when selecting "HTTP or HTTPS" [ID 42716]

In the DataMiner Cube desktop app, you can configure whether Cube should connect to a specific DMS using HTTPS only ("HTTPS only") or whether it can fall back to HTTP if HTTPS is not available ("HTTP or HTTPS").

Up to now, when you had selected "HTTP or HTTPS", first, an HTTP request would be sent with a default timeout of 100 seconds. If that request failed, an HTTPS request would then be sent.

From now on, both an HTTP request and an HTTPS request will be sent in parallel, each with a timeout of 60 seconds.

  • When the request that completes first is successful, the remaining request will be canceled.
  • When the request that completes first returns an empty response, the system will fall back on the remaining request.

Also, a number of additional enhancements have been made to improve overall connection stability.

Logging: All Cube log entries sent to a DataMiner Agent will now include the ConnectionID dimension [ID 42721]

Up to now, all SPI log entries sent to a DataMiner Agent included the ConnectionID dimension, which allows the corresponding connection to be traced.

From now on, apart from the SPI log entries, all other Cube log entries sent to a DataMiner Agent will also include the ConnectionID dimension.

Miscellaneous enhancements [ID 42730]

A number of minor enhancements have been made, especially with regard to calculating durations included in SPI logging.

Enhancements with regard to retrieving data from EPM element managers [ID 42731]

A number of enhancements have been made with regard to retrieving data from EPM element managers.

Fixes

Visual Overview: Problem when processing shape conditions or creating shape properties [ID 42436]

In some cases, an Object reference not set to an instance of an object exception could be thrown when processing shape conditions or creating shape properties.

Matrices would not display correct values [ID 42585]

In some cases, it could occur that a matrix did not display the correct values. This could for example happen with a matrix shown in a virtual primary element in a redundancy group. The way matrices are updated has been optimized to prevent this.

'Augmented operations alarm settings' window would not open in popped-out alarm template editor window [ID 42749]

When the alarm template editor was shown in a separate window (e.g. after you had click the pop-out icon in the top-right corner of an alarm template), up to now, when you clicked the button in the Analytics or Anomalies column, the Augmented Operations alarm settings window would incorrectly open inside the main window instead of the alarm template editor window.

Visual Overview: Problem when information about impacted services displayed in an element shape was updated [ID 42786]

When information about the impacted services was displayed in an element shape, in some rare cases, DataMiner Cube could stop working when that information was updated.

Alarm Console: Linked alarm tab with more than 50 active correlation alarms would not show all correlation alarms matching the selected card [ID 42796]

When a linked alarm tab contained more than 50 active correlation alarms, in some rare cases, not all correlation alarms matching the selected card would be shown.