Table of Contents

General Main Release 10.7.0 – Changes (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!

Changes

Enhancements

SLNet: Trend graphs in Cube will now also correctly display behavioral change points for table column parameters without advanced naming [ID 41751]

Because of a number of enhancements made in SLNet, trend graphs in DataMiner Cube will now also correctly display behavioral change points for table column parameters without advanced naming.

Automation: Engine class now has an OnDestroy handler that will allow resources to be cleaned up when a script ends [ID 43919]

An OnDestroy handler has now been added to the Engine class. This handler will allow resources to be cleaned up when a script ends.

Multiple handlers can be added. They will run synchronously, and if one handler throws an error, the others will keep on running.

Automation: All methods that use parameter descriptions have now been marked as obsolete [ID 43948]

All methods in the Skyline.DataMiner.Automation namespace that use parameter descriptions have now been marked as obsolete.

Service & Resource Management: New resource manager settings to configure the number of start action threads and simultaneous actions [ID 44056]

Because of a number of enhancements, overall performance has increased when starting multiple bookings in parallel.

Also, in the resource manager, it is now possible to configure the number of start action threads and simultaneous actions.

Setting Description
MaxAmountOfThreads The number of threads the resource manager will use to start bookings.
By default, 6 threads will be used. To restore this setting to the default value, set its value to null.
Note: The number of threads must at least be set to 2 in order for the scheduler to be able to start an action and keep a thread available for asynchronous continuations.
MaxAmountOfParallelTasks The number of parallel actions the resource manager will start on the threads.
By default, the number of parallel action is set to 7. To restore this setting to the default value, set its value to null.

The following example shows how you can configure this from an Automation script.

private void UpdateResourceManagerConfigSettings()
{
    var setConfigMessage = new ResourceManagerConfigInfoMessage(ResourceManagerConfigInfoMessage.ConfigInfoType.Set)
    {
        ResourceManagerAutomationSettings = new ResourceManagerAutomationSettings()
        {
            ResourceManagerAutomationThreadSettings = new ResourceManagerAutomationThreadSettings()
            {
                MaxAmountOfParallelTasks = 30,
                MaxAmountOfThreads = 8
            }
        },
    };
    engine.SendSingleResponseMessage(setConfigMessage);
}

In most cases, these settings can keep their default value, unless performance has to optimized when multiple concurrent bookings have to be started. In order to increase performance, the number of threads and parallel tasks can be increased, provided the DataMiner Agent and the database can handle the increased load.

Note
  • When the above-mentioned settings have been changed, the resource manager must be restarted.
  • Only users with Modules > System configuration > Tools > Admin tools permission are allowed to change the above-mentioned settings.
  • If the SkipDcfLinks setting is set to true, we recommend that you do not set MaxAmountOfParallelTasks too high. DCF link creation can be an expensive operation. Performing a large number of action in parallel might decrease performance.

Augmented Operations: Server-side support for new flatline detection modes [ID 44094]

When, in DataMiner client applications (e.g. DataMiner Cube), you are configuring the Augmented Operations alarm settings for a particular parameter in an alarm template, from now on, it will be possible to choose between the following flatline detection modes:

Mode Description
Smart flatline alarming In this mode, SLAnalytics will automatically determine when a flatline period is anomalous by comparing it to the parameter's historical behavior. A new flatline period will only trigger an alarm if it is significantly longer than previously observed flat periods.
Absolute flatline alarming In this mode, you can define a fixed duration threshold (in seconds) for when a flatline event should trigger an alarm. Additionally, you can assign a severity level to the generated flatline alarm event.

See also: Alarm templates: New flatline detection modes in Augmented Operations alarm settings [ID 44191]

DataMiner upgrade: Web-only upgrades with version 10.6.x or above will now require the DMA to have version 10.5.x or above [ID 44103]

From now on, it will no longer be allowed to perform web-only upgrades with version 10.6.x or above on DataMiner Agents with a version below 10.5.x.

This means, that any DataMiner Agent on which you want to perform a web-only upgrade with version 10.6.x or above will first have to be upgraded to version 10.5.x or above.

dataminer.services: Restrictions when adding a DMA to a DMS [ID 44171]

From now on, when you try to add a DataMiner Agent to a DataMiner System, the operation will fail in the following cases:

  • The DataMiner Agent is cloud-connected, but the DataMiner System is not.
  • The DataMiner Agent and the DataMiner System are cloud-connected, but they do not have the same identity, i.e. they are not part of the same cloud-connected system.

If the DataMiner System is a STaaS system, adding a DataMiner Agent will also fail if the DataMiner Agent is not cloud-connected.

Scheduler will now be able to start more than 10 synchronously running Automation scripts [ID 44200]

Up to now, using Scheduler, it would only be possible to start a maximum of 10 synchronously running Automation scripts.

From now on, it will be possible to start more than 10 synchronously running Automation scripts.

Relational anomaly detection: GetRADParameterGroupInfoResponseMessage now also includes the ID of the RAD parameter group [ID 44237]

The response to a GetRADParameterGroupInfoMessage will now also include the ID of the RAD parameter group.

Fixes

SLAnalytics would not receive 'swarming complete' notifications for swarmed DVE child elements [ID 43984]

Up to now, SLAnalytics would incorrectly not receive any "swarming complete" notifications for swarmed DVE child elements. As a result, alarm focus calculations for DVE child elements would be restarted from scratch instead of being fetched from the database.

Service & Resource Management: A capability could incorrectly be set to a null value [ID 44125]

In some cases, a capability could incorrectly be set to a null value.

From now on, when a capability is booked, it will no longer be possible to set its value to null.

DataMiner installation: Stopping the DataMiner Agent during an installation would incorrectly be interpreted as a crash [ID 44220]

At some point during a DataMiner installation, the DataMiner Agent needs to be stopped for a brief moment to allow a number of configuration steps to be performed. Up to now, in some rare cases, SLWatchdog would incorrectly interpret stopping the DataMiner Agent as a crash, causing the system to start up too soon.

Failover: Problem when reloading the scheduled tasks [ID 44234]

After a Failover switch, in some cases, the new online agent would incorrectly not reload the scheduled tasks that the former online agent had in memory.

Improve this page