Table of Contents

General Feature Release 10.3.2

Note

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

Tip

Features

Resource migration to Elasticsearch [ID 33797] [ID 33946] [ID 34105] [ID 34207] [ID 34296] [ID 34522] [ID 34568] [ID 34784] [ID 35067] [ID 35155]

It is now possible to migrate the resources and resource pools from the Resources.xml file to Elasticsearch. This improves the scalability and performance on systems that have a large number of resources.

To start the migration, you can use the SLNetClientTest tool. The migration app is available under Advanced > Migration.

Warning
  • Always be extremely careful when using the SLNetClientTest tool, as it can have far-reaching consequences on the functionality of your DataMiner System.
  • All Resource Manager instances in the cluster will restart during the migration.
Tip

For detailed information on the migration, refer to Resource migration to Elasticsearch.

If for any reason the migration fails, you can find information in the SLMigrationManager.txt and SLResourceManager.txt log files. In this case, the existing XML setup will continue to be used and the configuration will not switch to Elasticsearch.

Note that there are differences when resources and resource pools are stored in Elasticsearch, as compared to in XML:

  • When XML storage is used, it is not possible to remove a resource when one of the DMAs in the cluster cannot be reached, as this could cause syncing issues. No such restrictions apply when Elasticsearch storage is used.

  • The following restrictions apply for the properties stored in Elasticsearch:

    • Property names must not start with the character _.

    • Property names must not contain the characters . (period), # (hashtag), * (star), , (comma), " (double quote) or ' (single quote).

    • Property names must not be empty or contain only whitespace characters.

    • Property values must not be null.

    Note

    If Elasticsearch storage is enabled, and a resource or resource pool with invalid properties is added or updated, the API will return a ResourceManagerErrorData in the TraceData, with reason InvalidCharactersInPropertyNames.

  • Field names in Elasticsearch have a maximum length of 32766 bytes, which means any field of a resource or resource pool indexed in Elasticsearch can only contain 32766 bytes.

    Note

    If there is an attempt to save a resource or resource pool with a field that is too big, the API will return an UnknownError. The SLResourceManager.txt log file will contain the actual exception, which will mention the field that could not be indexed in Elasticsearch.

  • When a resource is indexed in Elasticsearch, all its properties, capacities, and capabilities will be indexed as well. This means that each unique property name and unique capacity and capability ID will become a field mapping in Elasticsearch. If there is an unusually large number of capacities, capabilities, and/or property names, this may lead to reduced performance of Elasticsearch. During testing, this was noticed when more than 300 unique field mappings were present.

  • If XML storage is used and you subscribe to the ResourceManagerEventMessage, you will receive an initial event with all resources and resource pools. This event is not sent when Elasticsearch storage is used, in order to prevent sending a message to the client containing thousands of resources.

  • If XML storage is used, all Resource Manager instances in the cluster will sync the resources in their XML file on startup and during the midnight sync. If Elasticsearch storage is used, DataMiner relies on Elasticsearch to do the syncing, so this does not happen during the midnight sync or on startup. However, Resource Manager will refresh the cached resources during the midnight sync by reading all resources and resource pools again from Elasticsearch.

Client-server communication: gRPC instead of .NET Remoting [ID 34797] [ID 34983]

Up to now, DataMiner clients and servers communicated with each other using the .NET Remoting protocol. From now on, they are also able to communicate with each other via an API Gateway module using gRPC connections, which are much more secure. For example, as to the use of IP ports, gRPC uses the standard port 443, whereas .NET Remoting uses the non-standard port 8004. Moreover, the API Gateway module is able to restart itself during operation and to automatically recover the connections to clients and SLNet.

When you upgrade DataMiner, the API Gateway module will automatically be installed in the C:\Program Files\Skyline Communications\DataMiner APIGateway\ folder. All logging and program-specific data associated with the API Gateway module will be stored in the C:\ProgramData\Skyline Communications\DataMiner APIGateway\.

Important

For now, gRPC communication has to be explicitly enabled. If you do not enable it, Cube clients and DMAs will continue to communicate using the .NET Remoting protocol.

Enabling the use of gRPC connections for communication between Cube and DMA

Do the following on each DMA you want DataMiner Cube instances to connect to via gRPC by default.

  1. Open the C:\Skyline DataMiner\Webpages\ConnectionSettings.txt file.
  2. Set the type option to GRPCConnection.
Enabling the use of gRPC connections for inter-DMA communication

In the DMS.xml file, you must add redirects for each DMA that should communicate with the other DMAs in the DMS over gRPC. Failover Agents also need a redirect to each other's IP address.

For example, in a cluster with two DMAs, with IPs 10.4.2.92 and 10.4.2.93, DMS.xml can be configured as follows.

  • On the DMA with IP 10.4.2.92:

      <DMS errorTime="30000" synchronized="true" xmlns="http://www.skyline.be/config/dms">
     <Cluster name="pluto"/>
     <DMA ip="10.4.2.92" timestamp=""/>
     <DMA ip="10.4.2.93" id="35" timestamp="2023-01-05 01:24:38" contacted_once="TRUE" lostContact="2023-01-06 00:45:01"/>
     <Redirects>
        <Redirect to="10.4.2.93" via="https://10.4.2.93/APIGateway" user="MyUser" pwd="MyPassword"/>
     </Redirects>
  </DMS>

  • On the DMA with IP 10.4.2.93:

      <DMS errorTime="30000" synchronized="true" xmlns="http://www.skyline.be/config/dms">
     <Cluster name="pluto" synchronize="" timestamp="2022-12-13 12:48:29"/>
     <DMA ip="10.4.2.93" timestamp="" contacted_once="" lostContact=""/>
     <DMA ip="10.4.2.92" timestamp="2023-01-03 23:38:42" contacted_once="TRUE" lostContact="2023-01-06 01:02:00" id="69" uri=""/>
     <Redirects>
        <Redirect to="10.4.2.92" via="https://10.4.2.92/APIGateway" user="MyUser" pwd="MyPassword"/>
     </Redirects>
  </DMS>
Note

The passwords in the pwd attribute are encrypted and replaced with an encryption token when they are first read out by DataMiner.

All DOM objects now have 'LastModified', 'LastModifiedBy', 'CreatedAt' and 'CreatedBy' properties [ID 34980]

All DOM objects (DomInstance, DomTemplate, DomDefinition, DomBehaviorDefinition, SectionDefinition and ModuleSettings) will now contain the following additional properties:

  • LastModified: Date/time (UTC) at which the object was last modified.
  • LastModifiedBy: Full username of the user who last modified the object.
  • CreatedAt: Date/time (UTC) at which the object was created.
  • CreatedBy: Full username of the user who created the object.
Note

  • CreatedAt and CreatedBy are automatically populated when the object is created. Any value assigned to these two fields by a user will always be discarded.

  • LastModified and LastModifiedBy are automatically updated when the object is updated on the server. Any value assigned to these two fields by a user will always be discarded. When an object is created, these fields will contain the same values as CreatedAt and CreatedBy.

  • These four fields are not directly accessible on the object. You first need to cast them to either ITrackBase or their individual interfaces (ITrackLastModified, ITrackLastModifiedBy, ITrackCreatedAt and ITrackCreatedBy).

    string createdBy = ((ITrackBase) domInstance).CreatedBy;

  • These four fields can all be used in a filter.

  • In the Elasticsearch database, existing data will not contain values for these new fields (except the LastModified field for all but ModuleSettings).

  • All four fields are also available in the GQI data source Object Manager Instances. The Last Modified and Created At columns should show the time in the time zone of the browser.

SLAnalytics - Proactive cap detection: Using alarm templates assigned to DVE child elements [ID 35194]

When proactive cap detection was enabled, up to now, in case of DVE elements, the alarm template of the parent would always be used.

From now on, if a DVE child element has an alarm template assigned to it, that alarm template will be used. Only when a DVE child element does not have an alarm template assigned to it will the alarm template of the parent be used.

Changes

Enhancements

Security enhancements [ID 35240]

A number of security enhancements have been made.

SLLogCollector will now first check for default.xml files in the LogConfig folder in the same location as SL_LogCollector.exe [ID 34739]

Up to now, SLLogCollector expected custom collector configuration files named default.xml to always be placed in the C:\Skyline DataMiner\Tools\SLLogCollector\LogConfigs folder.

From now on, it will first check the LogConfig folder in the same location as SL_LogCollector.exe. If that LogConfig folder does not exist, if the folder is empty or if the default.xml file in that folder cannot be deserialized, it will fall back on the default.xml file in the C:\Skyline DataMiner\Tools\SLLogCollector\LogConfigs folder.

More detailed logging when the certificate chain is invalid while connecting to Cassandra [ID 34822]

More detailed information will now be added to the SLDBConnection.txt log file when the certificate chain is invalid while connecting to Cassandra.

Log entry syntax: Certificate chain error: {chainStatus.Status}, details: {chainStatus.StatusInformation}

BREAKING CHANGE: Capacity property will no longer be initialized on new Resources [ID 34856]

From now on, the Capacity property will no longer be initialized on new Resources.

As a result, in DataMiner Cube, the resources module will no longer require the legacy capacity to be initialized. Newly created resources will no longer have a legacy capacity. The concurrency of a resource will still be stored in Resource.MaxConcurrency.

Impact of this change

Since Capacity is no longer initialized on a new Resource, GetEffectiveMaxConcurrency will take into account MaxConcurrency. MaxConcurrency will now be initialized with 1 as is the case with Capacity.MaxConcurrency.

If GetEffectiveMaxConcurrency should still use the value of Capacity.MaxConcurrency, MaxConcurrency should be set to 0.

To restore legacy behavior, a new resource should be initialized as follows:

var resource = new Resource()
{
  MaxConcurrency = 0,
  Capacity = new ResourceCapacity(),
};

This change in behavior will impact results for both GetAvailableResources and GetResourceUsage on ResourceManagerHelper, both marked as obsolete since 9.6.5. For both methods, newly created resources will now, by default, always be considered unavailable.

Web apps - Interactive Automation scrips: Fields containing invalid values will now be indicated more clearly [ID 34962]

When, in an Automation script launched from a web app, an input field contains an invalid value, the border of that field will turn red. This red border will now be wider in order to be more visible.

GQI: Enhanced performance of GQI queries [ID 34977]

Because of a number of enhancements, overall performance of GQI queries has increased, especially when those queries contain join operations.

NAS service will now have a quoted image path [ID 34989]

Up to now, the NAS service had an unquoted image path. From now on, it will instead be installed with a quoted path.

When you want the NAS service on existing setups to have a quoted path, do the following:

  1. Execute the following command:

    sc config NAS binPath="\"C:\Skyline DataMiner\NATS\nats-account-server\nssm.exe\""

  2. Restart NAS and NATS.

GQI: Enhanced performance of GQI queries using the 'Get parameters for elements where' data source [ID 35005]

Because of a number of enhancements, overall performance of GQI queries using the Get parameters for elements where data source has increased.

Dashboards app - Line & area chart: Multiple timespans will now be converted to one single time range [ID 35008]

When a line & area chart component is fed a collection of timespans, it will now convert those timespans to one single time range.

For example, when a line & area chart component is fed the following timespans...

  • 01/01/2022 9:00:00 > 01/01/2022 10:00:00
  • 01/01/2022 9:30:00 > 01/01/2022 10:30:00

... it will convert those timespans into the following time range:

  • 01/01/2022 9:00:00 > 01/01/2022 10:30:00

Service & Resource Management: Enhanced performance when adding and updating bookings [ID 35016]

Because of a number of enhancements, overall performance has increased when creating and updating bookings.

Web apps: Button styles used in interactive Automation script components have been aligned with those used in low-code app components [ID 35076]

In the web apps, the button styles used in interactive Automation script components have now been fully aligned with those used in low-code app components.

SLAnalytics - Proactive cap detection: Enhanced accuracy when generating alarm predictions [ID 35080]

Because of a number of enhancements, overall accuracy has increased when generating alarm predictions.

Web app: More detailed version information in About box [ID 35090]

In the About box of a web application, you can now find more detailed version information.

Old name New name Description
- Server version Server version and build number of the DataMiner Agent
Client build Web version Build number of the web app
Client version App Version number of the web app
Server API version API Version number of the Web Services API

GQI: Enhanced query performance when aggregation operations are followed by a filter [ID 35110]

Because of a number of enhancements, overall query performance has increased, especially in cases where aggregation operations are followed by a filter.

SLAnalytics - Behavioral anomaly detection : More accurate change point time ranges [ID 35121]

Because of a number of enhancements, behavioral changes of the type "level shift", "trend change" and "variance change" will now have a more accurate time range when the change in behavior is sufficiently clear.

Dashboards - GQI components: Enhanced behavior when loading data [ID 35148]

Up to now, a loading skeleton would be displayed each time data was being loaded into a GQI component (e.g. a node edge graph). From now on, only when the component was empty will a loading skeleton be displayed. When existing data in the component is being refreshed, a loader bar will now be displayed instead.

Web apps: Enhanced performance when retrieving a list of users [ID 35150]

When a web app requests a list of users, the Web Services API will now cache the result set it receives from the server. This will increase overall performance, especially in situations where, up to now, the same list of users had to be retrieved frequently.

This user cache will be cleared each time a change occurs that has security implications (e.g. new users added, user permissions updated, etc.).

DataMiner Object Models: DomInstanceButtonDefinitions can only reference a single action [ID 35156]

From now on, DomInstanceButtonDefinitions can only reference a single action. If multiple actions are defined, a DomBehaviorDefinitionError with reason InvalidButtonActionCombination will be returned.

Also, when using the DomBehaviorDefinition inheritance system, the server-side logic will now make sure that there are no buttons or actions with identical IDs on both the parent and child definition.

  • If a duplicate action is found, a DomBehaviorDefinitionError with reason DuplicateActionDefinitionIds will be returned.
  • If a duplicate button is found, a DomBehaviorDefinitionError with reason DuplicateButtonDefinitionIds will be returned.

SAML authentication will now also work with user names instead of email addresses when automatic user creation is not enabled [ID 35159]

Since DataMiner version 10.2.6 (10.2.0 CU6), SAML authentication would only work when the SAML response claims contained an email address. From now on, SAML authentication will also work with user names instead of email addresses in case automatic user creation is not enabled.

Dashboards app - Line & area chart component: 'Group by' setting will now by default be set to 'All together' [ID 35160]

In case a Line & area chart component displays trending for multiple parameters, the Group by setting allows you to specify how the graphs should be grouped. From now on, this Group by setting will by default be set to "All together".

Enhanced performance when updating a baseline or assigning an alarm template that contains conditional monitoring [ID 35171]

Because of a number of enhancements, overall performance has increased when updating a baseline or assigning an alarm template that contains conditional monitoring.

Enhanced performance when deleting a service from an Elasticsearch database [ID 35173]

Because of a number of enhancements, overall performance has increased when deleting a service from an Elasticsearch database.

SLLogCollector: Custom CollectorConfig XML files will now be synchronized across the DataMiner cluster [ID 35180]

From now on, all custom CollectorConfig XML files will be synchronized across the DataMiner cluster.

Exporting and importing DELT packages containing element and alarm data is now supported on DataMiner Systems with a clustered database [ID 35213]

From now on, exporting and importing DELT packages containing element and alarm data is also supported on DataMiner Systems with a clustered database.

Note

Exporting and importing DELT packages containing trend data is not yet supported on DataMiner Systems with a clustered database.

SLAnalytics: Enhanced processing of parameter values 'exception' and 'other' [ID 35214]

Because of a number of enhancements, overall processing of "exception" or "other" parameter values by the SLAnalytics process has improved.

NATS: No attempt will be made to cluster NATS at DMA startup when NATSForceManualConfig is enabled [ID 35221]

At DMA startup, from now on, no attempt will be made to automatically cluster the NATS nodes when the NATSForceManualConfig option is enabled.

If necessary, NatsCustodianRequests can be triggered via the SLNetClientTest tool.

Low-Code Apps: URLs of published app versions will no longer contain the app version number [ID 35236]

From now on, the URL of a published version of an app will no longer contain the app version number. Only when you open an earlier version of an app will the URL contain the app version number.

ClusterState.xml file removed [ID 35248]

The Clusterstate.xml file, located in the C:\Skyline DataMiner folder, was obsolete and has now been removed.

SLAnalytics - Pattern matching: When a pattern is detected on a DVE child element the suggestion event will now be generated on that same DVE child element [ID 35264]

When a trend pattern was detected on a DVE child element, up to now, the suggestion event would be generated on the parent element. From now on, it will be generated on the child element instead.

Low-Code Apps: Enhanced confirmation message when deleting an app [ID 35269]

The confirmation message that appears when you delete an app will now indicate more clearly what will be removed:

  • When the app has never been published, only one draft exists. In this case, the confirmation message will clearly state that the entire app will be deleted.

  • When the app has been published, multiple versions of the app exist. In the confirmation message, you will be able to choose whether to delete only the current draft or the entire app.

Web apps: Date/time picker component will now always show 6 full weeks [ID 35277]

In all web apps, the date/time picker component will now always show 6 full weeks, regardless of the number of days in the current month. This will prevent the component from having to resize when you switch from one month to another.

SLLogCollector now also collects hot threads, node usage and tasks from Elasticsearch [ID 35310]

SLLogCollector packages will now also include the following additional files containing information retrieved from the Elasticsearch database (if present):

File Contents
\Logs\Elastic\<Node address>\_nodes.hot_threads.txt The output of an GET /_nodes/hot_threads command.
\Logs\Elastic\<Node address>\_nodes.usage.json The output of a GET /_nodes/usage command.
\Logs\Elastic\<Node address>\_tasks.json The output of a GET /_tasks?detailed command.

Fixes

Problem with Elasticsearch health monitoring [ID 34744]

When an Elasticsearch cluster used by DataMiner was hosted on servers that host IPv6 addresses, the Elasticsearch health monitoring in DataMiner would fail to assess the Elasticsearch cluster state and conclude that the indexing database was unavailable.

External authentication via SAML: Problem when using Okta as identity provider [ID 34745]

When using external authentication via SAML, a software issue would prevent you from logging in when Okta was set up as identity provider.

Cassandra cluster: Null reference exceptions [ID 34964]

On systems with a Cassandra cluster, in some cases, messages to SLDataGateway could cause nullreference exceptions to be thrown.

Example of an exception stored in the SLDBconnection.txt log file:

SLDBConnection|Skyline.DataMiner.Net.Messages.SLDataGateway.DataRequest`1[Skyline.DataMiner.Net.Messages.SLDataGateway.Alarm]|INF|0|285|System.NullReferenceException: Object reference not set to an instance of an object.
   at SLCassandraClassLibrary.DBGateway.DBGateway.ExecuteRequest[T](DataRequest`1 request)
   at SLCassandraClassLibrary.DBGateway.IncomingConnection.$_executor_ExecuteRequest(BaseRequest request)
Tip

See Null reference exceptions in SLDBConnection.txt and unhandled exception when retrieving Correlation details.

Problem with SLDataMiner when loading an alarm template schedule failed [ID 34988]

In some cases, an error could occur in SLDataMiner when loading an alarm template schedule failed.

Alarm templates: Parameters exported to DVE child elements could have incorrect alarm limits [ID 34996]

When a parameter was exported as a standalone parameter to a DVE child element, in some cases, the alarm limits could be incorrect when the type of alarm monitoring was set to either Relative or Absolute.

Also, LED bar controls would either not display or not update their alarm limits.

Dashboards app: Button to restore the initial view would incorrectly appear on all tables after sorting or filtering a table [ID 35003]

When, on a dashboard, you sorted or filtered a table, a button to restore the initial view would incorrectly appear on all tables on that dashboard. Also, when you clicked one of those buttons, they would all disappear. From now on, when you sort or filter a table on a dashboard, a button to restore the initial view will only appear on that particular table.

Web apps - Visual Overview: Certain actions would no longer work [ID 35012]

In some cases, Card, Script, Link and Popup actions would no longer work in visual overviews opened in web apps.

Hosting agent filters would be disregarded when alarm events were retrieved from an Elasticsearch database [ID 35049]

When alarm events were retrieved from an Elasticsearch database, any hosting agent filters would be disregarded.

SLLogCollector would only take a dump of the first process when multiple processes were specified in the -d command-line option [ID 35074]

When you ran SLLogCollector via the command line and specified multiple processes for which dumps had to be taken (e.g. SL_LogCollector.exe -c -d=46436,61652), it would incorrectly only take a dump of the first process.

Problem with the generation of TaskCancellationExceptions [ID 35079]

Modules using the managed SPI framework (Skyline.DataMiner.Spi) would trigger excessive numbers of TaskCancellationExceptions. Also, for the SLNet process, increasing numbers of these exceptions would be generated for every additional Cube client.

Monitoring app: Problem when opening the histogram page of a view [ID 35081]

When, in the Monitoring app, you selected a view and opened the histogram page, in some cases, a Maximum call stack size exceeded error would appear.

Automation: Memory leak when using the engine.AddScriptOutput method to pass script output of type string [ID 35119]

When an engine.AddScriptOutput method was used to pass output data of type string from a script to the application that executed it or from a subscript to the script that executed that subscript, that output data of type string would incorrectly not get cleared from memory.

Tip

See SLAutomation memory leak when Engine.AddScriptOutput is used

Dashboards app: Visual Overview component would not show any content when linked to a feed [ID 35130]

When a Visual Overview component was linked to a feed, in some cases, it would not show any content.

SLElement would leak memory when an element was frequently receiving timeout values [ID 35131]

When an element was frequently receiving timeout values, SLElement would leak memory.

Since DataMiner 10.2.10/10.2.0 CU8, stable trend data points were no longer properly refreshed in the database, which could cause them to be removed from the database when they expired.

Tip

See Stable trend points not kept alive.

Protocols: Problem when using the 'partialSNMP' option when polling tables using the 'multipleGetNext' or 'multipleGetBulk' method [ID 35147]

When the partialSNMP option was used when polling tables using the multipleGetNext or multipleGetBulk method, up to now, rows and values would be skipped when one or more columns did not contain values for one or more rows. This caused the next partial requests to jump forward by the amount of empty cells, resulting in missing rows and unexpected empty cells.

Also, a problem with the detection of infinite loops for SNMPv3 when receiving end-of-mib-view errors has been fixed.

One-day average trend records would incorrectly only be written into the database if

  • a TTL was specified, and
  • the MaintenanceSettings.xml file contained an entry specifying the window size (e.g. <TimeSpan1DayRecords windows="120" />).

From now on, one-day average trend records will be written into the database as soon as a TTL setting has been configured for Day records.

Also, the default window size for the records has been restored to 120 minutes (i.e. 2 hours).

Tip

See Missing 1-day average trending records.

Dashboards app & Low-Code Apps - Parameter feed: Problem when more than 10,000 elements had to be retrieved from the server [ID 35186]

Up to now, the parameter feed used the element cache of the web client to populate its element list. As this cache can only hold up to 10,000 elements, this prevented the parameter feed from retrieving all elements when the cluster contained more than 10,000 elements.

From now on, when the parameter feed has a protocol or view filter, it will fetch all elements matching the filter page by page, even when the total number of elements exceeds 10,000.

Problem with wildcard OIDs when specified on a table parameter [ID 35223]

SNMP table polling would stop working when a wildcard OID was configured on the table parameter. That wildcard OID would always be replaced by 1 instead of the configured parameter value.

Configuring an OID on the table is necessary when using getNext (with or without multipleGet). In other cases, it is optional. There, a workaround could be to remove the OID configured on the table parameter.

Standalone parameters configured with a wildcard OID were not affected.

Dashboards app & Low-Code Apps - Node edge component: Segments of bidirectional edges would not always be positioned consistently [ID 35230]

In a node edge graph, the segments of bidirectional edges would not always be positioned consistently.

DataMiner Object Models: Problem when retrieving a non-existing DomInstance status ID [ID 35231]

When a GQI query retrieved the status of a DOM instance that had no status, the logic would incorrectly detect that a status was present and would try to resolve the display name for that status, causing a Could not find state for statusID ... error to be thrown.

Problem when a GQI message was sent asynchronously to SLNet [ID 35232]

When a client asynchronously sent an GQI message to SLNet, in some cases, an exception could be thrown.

Problem during DataMiner startup when an element had its state changed from 'undefined' to 'stopped' [ID 35233]

When redundancy groups were being initialized during a DataMiner startup, in some cases, an error could occur when an element had its state changed from "undefined" to "stopped".

Cassandra Cluster: Incorrect db.xml entries could cause db.xml to get corrupted upon synchronization [ID 35237]

On DataMiner clusters with a Cassandra Cluster database, incorrect db.xml entries could cause that file to get corrupted upon synchronization.

Dashboards app & Low-Code Apps: Loading indicator would not appear when sorting, filtering or refreshing a table [ID 35238]

When you sorted or filtered a table by clicking a table header, or when an action triggered a refresh of the table data, in some cases, no loading indicator would appear.

Dashboards app & Low-Code Apps: Issues with regard to data highlighting [ID 35250]

A number of issues with regard to data highlighting have been fixed.

Dashboards app & Low-Code Apps: Enhanced caching of items in query column selection box [ID 35251]

When creating or editing a query, you can select the query columns from a selection box. A number of enhancements have now been made with regard to the caching of this list of query columns.

Dashboards app & Low-Code Apps: Selected data would incorrectly not get removed after being deleted [ID 35254]

When data (e.g. a query) was deleted while it was selected, in some cases, it would incorrectly not be removed from the selection.

Dashboards app: Two context menus could incorrectly be displayed simultaneously in the side bar [ID 35255]

When, in the side bar, you right-clicked a folder or a dashboard, and then clicking the ellipsis ("...") in the tab header, two context menus could incorrectly be displayed simultaneously.

Dashboards app & Low-Code Apps - Node edge component: Problem with 'Set as ...' commands in component settings [ID 35256]

When, in the settings of a node edge component, you had selected a configured edge, it would incorrectly be possible to use the Set as edge command. This would clear the existing configuration of the edge in question and cause the settings to be saved incorrectly.

From now on, it will only be possible to set a node as edge and vice versa.

Dashboards app & Low-Code Apps: Unknown components would incorrectly no longer be indicated as such [ID 35257]

In some cases, unknown components would incorrectly no longer be indicated as such.

SLAnalytics would incorrectly ignore trend patterns defined for parameters of child DVE elements [ID 35260]

In DataMiner feature version 10.3.1, SLAnalytics would incorrectly ignore trend patterns defined for parameters of child DVE elements.

The Documents module allows you to integrate documents in DataMiner. This way, you can access relevant information about the elements and services in your system at any time. You can store physical files, email addresses and hyperlinks to web pages.

Up to now, when email addresses and hyperlinks to web pages were retrieved from the XML files in which they are stored, SLDataMiner would leak memory due to a problem with the cleanup of temporary data.

Eventing and polling would incorrectly be used simultaneously [ID 35267]

When a client application connects to a DataMiner Agent, it will first try to set up communication via eventing. If communication via eventing fails, the DataMiner Agent will fall back to communication via polling. In some rare cases, both types of communication (i.e. eventing and polling) would incorrectly be used simultaneously.

Low-Code Apps: Keyboard shortcuts would not work in the dashboard editor [ID 35274]

Up to now, the following keyboard shortcuts would not work in the dashboard editor:

Shortcut Action
Ctrl+A Select all components.
Delete Delete the selected components.

GQI: Metadata would incorrectly be removed when a custom operator was applied [ID 35283]

When, in a GQI query, a custom operator was applied, all metadata available on the rows would incorrectly be removed, causing feeds to no longer work as expected.

Also, when a column was renamed via a custom operator, the metadata available on that column would incorrectly be removed.

Spectrum Analysis: 'Visualize measurement points' setting of a spectrum element would no longer be property saved [ID 35293]

When you enabled the Visualize measurement points setting of a spectrum element, that change would no longer to properly saved in the element's element.xml file. This would cause unexpected behavior after restarting the DataMiner Agent or the element in question.

Dashboards app / Low-Code Apps - Node edge component: Edge overrides would incorrectly no longer be applied [ID 35298]

When, in the settings of a node edge graph, you had configured edge overrides, these would incorrectly no longer be applied.

Dashboards app & Low-Code Apps - GQI table component: 'Cannot read properties of undefined (reading 'Guid')' error [ID 35316]

In some cases, a GQI table component could show a Cannot read properties of undefined (reading 'Guid') error.

Elasticsearch: Problem when fetching metadata referring to stopped elements [ID 35423]

When alarms are being indexed in Elasticsearch, metadata is added. For example, the name of the protocol of the element in question.

Up to now, when SLNet requested that metadata, an error could occur when fetching information regarding a stopped element that had DVE child elements with alarms that had not yet been written to the database.

Propose changes