General Feature Release 10.3.8

Note

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

Important

When downgrading from DataMiner Feature Release version 10.3.8 (or higher) to DataMiner Feature Release version 10.3.4, 10.3.5, 10.3.6 or 10.3.7, an extra manual step has to be performed. For more information, see Downgrading a DMS.

Tip

• For release notes related to DataMiner Cube, see DataMiner Cube Feature Release 10.3.8.
• For release notes related to the DataMiner web applications, see DataMiner web apps Feature Release 10.3.8.
• For information on how to upgrade DataMiner, see Upgrading a DataMiner Agent.

New features

Process Automation: Support for PaToken bulk operations [ID 35685]

From now on, PaToken objects can be created, updated and deleted in bulk using the following methods provided by the PaTokens helper:

• CreateOrUpdate

  /// <summary>
  /// Returns the created or updated <paramref name="objects"/>.
  /// </summary>
  /// <param name="objects"><see cref="List{PaToken}"/> of <typeparamref name="PaToken"/> to be created or updated.</param>
  /// <returns>The result containing a list of <paramref name="objects"/> that were successfully updated or created. And a list of <see cref="TraceData"/> per item.</returns>
  public BulkCreateOrUpdateResult<PaToken, Guid> CreateOrUpdate(List<PaToken> objects)
  

  The result will contain a list of tokens that were successfully created or updated. The trace data is available per token ID. If an issue occurs when an item gets created or updated, no exception will be thrown (even when ThrowExceptionsOnErrorData is true). The trace data of the last call is available and will contain the data for all items. If the list contains tokens with identical keys, only the first will be considered.

• Delete

  /// <summary>
  /// Deletes the given <paramref name="objects"/>.
  /// </summary>
  /// <param name="objects"><see cref="List{PaToken}"/> of <typeparamref name="PaToken"/> to be deleted.</param>
  /// <returns>The result containing a list of IDs of <paramref name="objects"/> that were successfully deleted. And a list of <see cref="TraceData"/> per item.</returns>
  public BulkDeleteResult<Guid> Delete(List<PaToken> objects)
  

  The result will contain a list of tokens that were successfully deleted. The trace data is available per token ID. If an issue occurs when an item gets deleted, no exception will be thrown (even when ThrowExceptionsOnErrorData is true). The trace data of the last call is available and will contain the data for all items.

SLNetClientTest tool: New menu to manage the cloud connection of a DMA while it is offline [ID 36611]

In the SLNetClientTest tool, you can now go to Offline tools > CcaGateway (offline) to manage the cloud connection of the local DataMiner Agent while it is offline.

Warning

Always be extremely careful when using the SLNetClientTest tool, as it can have far-reaching consequences on the functionality of your DataMiner System.

'ExportRule' elements can now have a 'whereAttribute' attribute [ID 36622]

ExportRule elements can now have a whereAttribute attribute. This will allow you to validate the value of an attribute when applying an export rule.

See the following example. If the includepages attribute of the Protocol.SNMP element is true, the export rule will change that value to false in the exported protocol. Without the whereAttribute, the whereValue check would be performed on the value of the Protocol.SNMP element itself (which is mostly set to "auto") instead of the value of the includepages attribute.

<ExportRule table="*" tag="Protocol/SNMP" attribute="includepages" value="false" whereTag="Protocol/SNMP" whereAttribute="includepages" whereValue="true"/>

In this next example, all Column elements of parameters that have a level attribute that is set to 5 will have their value set to 2 in the exported protocol.

<ExportRule table="*" tag="Protocol/Params/Param/Display/Positions/Position/Column" value="2" whereTag="Protocol/Params/Param" whereAttribute="level" whereValue="5"/>

Changes

Enhancements

SLLogCollector now collects more API Gateway data [ID 34967]

SLLogCollector packages now include the following API Gateway data:

• appsettings.json
• DLL version
• Health
• Log file
• Version

SLAnalytics - Pattern matching: No automatic pattern matching anymore after creating or editing a pattern [ID 36265]

Up to now, when a trend pattern was created or edited, the system would automatically start searching for that new or updated pattern. Now, this will no longer happen. Pattern matching will only be done after explicitly sending a getPatternMatchMessage.

Security enhancements [ID 36294] [ID 36624]

A number of security enhancements have been made.

Service & Resource Management: Enhanced performance when creating and updating bookings [ID 36391]

Because of a number of enhancements, overall performance has increased when creating and updating bookings, especially on systems with a large number of overlapping bookings.

Service & Resource Management: Enhanced performance of GetEligibleResources call [ID 36430]

Because of a number of enhancements, overall performance of the GetEligibleResources call has increased.

SLAnalytics: Overall accuracy of the proactive cap detection function has increased [ID 36476]

Because of a number of enhancements, overall accuracy of the proactive cap detection function has increased.

DataMiner Agents joining a cluster will now synchronize their ProtocolScripts\DllImport folder [ID 36494]

When a DataMiner Agent joins a cluster, it will now synchronize its ProtocolScripts\DllImport folder.

Also, when processing a protocol, a DataMiner Agent will now synchronize

• the files in the ProtocolScripts/DllImport folder, and
• the files in the folders mentioned in the *QAction@dllImport* attribute.

Cassandra: 'analytics_changepointalarmentries_v2' table renamed to 'ai_cpalarms' [ID 36503]

In a Cassandra Cluster and an Amazon Keyspaces database, the analytics_changepointalarmentries_v2 table has now been renamed to ai_cpalarms.

As this new table name is quite a bit shorter, for both types of databases, keyspace prefixes can now have a maximum length of 20 characters instead of 11 characters.

Stream Viewer will now display parameter IDs in decimal format instead of octal format [ID 36525]

Stream Viewer will display an error message when an SNMP poll group contained either an invalid parameter or a parameter that did not have its SNMP setting enabled.

Up to now, that error message would contain the ID of the parameter in octal format. From now on, it will contain the ID of the parameter in decimal format instead.

Enhancements in order to deal with situations where HTTP traffic is modified [ID 36540]

A number of enhancements have been made in order to deal with situations where proxy servers, gateways, routers or firewalls modify HTTP traffic.

Factory reset tool will no longer try to delete non-existing folders [ID 36550]

Up to now, the factory reset tool SLReset.exe would log an exception each time it had tried to delete a non-existing folder. From now on, when it has to delete a folder, it will first check whether that folder exists. If not, it will not try to delete it.

SNMP tables: Columns of type 'retrieved' can now be placed in between columns of type 'snmp' [ID 36559]

Up to now, when an SNMP table had columns of type "retrieved" in between columns of type "snmp", problems could occur. All columns of type "retrieved" had to be grouped and placed at the right of the columns of type "snmp".

From now on, in an SNMP table, columns of type "retrieved" can be placed in between columns of type "snmp", providing the primary key column is a column of type "snmp" and not a column of type "retrieved".

Service & Resource Management: Enhanced performance [ID 36568]

Because of a number of enhancements with regard to fetching LinkerTableEntries of function resources, overall performance has increased.

SLAnalytics - Automatic incident tracking: Alarms will no longer be regrouped after a manual operation [ID 36595]

Up to now, manually removing an alarm from an incident could result in that alarm being regrouped with another existing or newly created incident. Also when you manually cleared an incident could all base alarms of that incident be regrouped.

From now on, alarms will no longer be regrouped after a manual operation.

SLAnalytics - Automatic incident tracking: Automatic incidents can now also be cleared manually [ID 36600]

From now on, users will be allowed to manually clear automatic incidents.

SLAnalytics - Behavioral anomaly detection & Proactive cap detection: Enhanced caching mechanism [ID 36639]

A number of enhancements have been made to the caching mechanism used by the Behavioral anomaly detection and Proactive cap detection features.

SLAnalytics - Behavioral anomaly detection: Enhanced anomaly labelling for periodically returning behavioral changes [ID 36664]

A behavioral change in the trend data of a parameter is considered an anomaly if there have not been similar behavioral changes that occurred regularly or frequently in the historical behavior of the parameter. This anomaly labelling has now been enhanced for periodically returning behavioral changes.

Smart baselines: Information event generation at 5-minute intervals has been disabled [ID 36691]

When smart baselines were configured, by default information events would be generated every 5 minutes. This information event generation has now been disabled to avoid information event floods in e.g. EPM environments.

Fixes

NATS connection could fail due to payloads being too large [ID 36427]

In some cases, the NATS connection could fail due to payloads being too large. As a result, parameter updates and alarms would no longer be saved to the database.

SLAnalytics: Incorrect trend predictions in case of incorrect data ranges set in the protocol [ID 36521]

If, in the protocol, a data range is specified for a parameters for which trend data prediction is required, the trend prediction algorithm will cap the prediction values to the data range. For example, if a parameter has a rangeLow value equal to 0 and a rangeHigh value equal to 100, the prediction will not contain values lower than 0 or higher than 100.

From now on, if the trend data contains values outside of the specified data range, the trend prediction algorithm will no longer consider the data range values to be valid or reliable, and will not limit the prediction to this range.

SLNet would incorrectly return certain port information fields of type string as null values [ID 36524]

When element information was retrieved from SLNet, in some cases, certain port information fields of type string would incorrectly be returned as a null value instead of an empty string value. As a result, DataMiner Cube would no longer show the port information when you edited an element.

Affected port information fields:

• BusAddress
• Number
• PollingIPAddress
• PollingIPPort

Problem with protocol.SendToDisplay API call [ID 36528]

When the following protocol API call was used to update specific matrix crosspoints, in some cases, the API call could ignore the physical size of the matrix. Also, the API call could change the dimensions of future ParameterChangeEventMessages.

protocol.SendToDisplay(matrixReadParameterId, changedInputs, changedOutputs);

Problem when requesting alarms on a system with Cassandra Cluster and Elasticsearch [ID 36549]

On systems with a Cassandra Cluster and an Elasticsearch database, the following issues could occur:

• When alarms were requested via a query with a service filter, no alarms would be returned.

• When alarms were requested via a query with a view filter, no alarms would be returned when that view or any of its subviews contained services. Also, when a view was enhanced with an element, that element would not be queried.

Problem with SLElement due to timeout actions of an element being overwritten [ID 36591]

In some rare cases, an error could occur in SLElement when a timeout action of an element with multiple connections would overwrite another timeout action of the same element.

SLAnalytics - Behavioral anomaly detection: False change point could be generated before a gap in a trend graph [ID 36605]

When there was a gap in a trend graph that showed a perfectly increasing line, in some cases, a false change point could be generated right before that gap.

SLAnalytics - Automatic incident tracking: Attempt to clear an alarm group that had already been cleared [ID 36654]

In some rare cases, the system would incorrectly try to clear an alarm group that had already been cleared.

NATSMaxPayloadException could be thrown when a client requested large amounts of data [ID 36655]

When a client requested large amounts of data, in some cases, a NATSMaxPayloadException could be thrown.

Cassandra Cluster: DVE properties would be cleared when an update was sent to the database [ID 36658]

DVE properties would be cleared each time an update was sent to a database of type Cassandra Cluster.

SLAnalytics would shut down immediately when it failed to get information from SLNet at start-up [ID 36692]

When starting up, SLAnalytics requests information from SLNet. Up to now, when it failed to get that information, it would immediately shut down. From now on, when the first request fails, it will try again once before shutting down.

Cassandra Cluster Migrator would fail to start up [ID 36804]

When the Cassandra Cluster Migrator tool (SLCCMigrator.exe) was started, in some cases, it would get stuck in the initialization phase due to a connection issue.