From 38991b4d1fffabe5213805a0a6c73676be6aedfc Mon Sep 17 00:00:00 2001 From: Wouter Demuynck Date: Tue, 17 Sep 2024 16:28:42 +0200 Subject: [PATCH 1/4] Add notes to legacy correlation engine references --- .../About_DataMiner_Systems/DataMiner_processes.md | 5 ++++- .../Advanced_Modules/Correlation/About_DMS_Correlation.md | 2 +- .../Adding_a_new_Correlation_rule.md | 2 +- .../SLNetClientTest_tracking_dma_communication.md | 2 +- .../Overview_of_the_files_found_in_the_root_folder.md | 2 +- .../Troubleshooting_Process_Identification.md | 1 - 6 files changed, 8 insertions(+), 6 deletions(-) diff --git a/user-guide/Advanced_Functionality/DataMiner_Systems/About_DataMiner_Systems/DataMiner_processes.md b/user-guide/Advanced_Functionality/DataMiner_Systems/About_DataMiner_Systems/DataMiner_processes.md index bc12e17cd1..6cb3c0ace4 100644 --- a/user-guide/Advanced_Functionality/DataMiner_Systems/About_DataMiner_Systems/DataMiner_processes.md +++ b/user-guide/Advanced_Functionality/DataMiner_Systems/About_DataMiner_Systems/DataMiner_processes.md @@ -154,7 +154,10 @@ The DataMiner Automation process. ### SLBrain -The DataMiner Correlation process. +The DataMiner Legacy Correlation process. + +> [!NOTE] +> Only available on DataMiner versions before 10.5.1. > [!TIP] > See also: [DataMiner Correlation](xref:About_DMS_Correlation) diff --git a/user-guide/Advanced_Modules/Correlation/About_DMS_Correlation.md b/user-guide/Advanced_Modules/Correlation/About_DMS_Correlation.md index 4eab709588..206865bce2 100644 --- a/user-guide/Advanced_Modules/Correlation/About_DMS_Correlation.md +++ b/user-guide/Advanced_Modules/Correlation/About_DMS_Correlation.md @@ -36,7 +36,7 @@ The event is a combination of: ## Correlation in DataMiner Cube vs. System Display -Two different engines are available for DataMiner Correlation: the deprecated System Display engine and the DataMiner Cube Correlation engine. Rules that were created in the System Display engine are still available in DataMiner Cube, though they are indicated as deprecated. The Cube Correlation Engine offers several functions that were not available in System Display, such as: +Two different engines are available for DataMiner Correlation: the deprecated System Display engine and the DataMiner Cube Correlation engine. In versions prior to DataMiner 10.5.1, rules that were created in the System Display engine are still available in DataMiner Cube, though they are indicated as deprecated. Starting from DataMiner 10.5.1, the deprecated correlation engine is no longer available. The Cube Correlation Engine offers several functions that were not available in System Display, such as: - Alarm filtering by means of regular expressions diff --git a/user-guide/Advanced_Modules/Correlation/Managing_Correlation_rules/Adding_a_new_Correlation_rule.md b/user-guide/Advanced_Modules/Correlation/Managing_Correlation_rules/Adding_a_new_Correlation_rule.md index 4d1654cb02..700beaf26a 100644 --- a/user-guide/Advanced_Modules/Correlation/Managing_Correlation_rules/Adding_a_new_Correlation_rule.md +++ b/user-guide/Advanced_Modules/Correlation/Managing_Correlation_rules/Adding_a_new_Correlation_rule.md @@ -36,4 +36,4 @@ You can also add a new rule by duplicating an existing rule and then changing th Alternatively, you can also select the rule, click the More... button at the bottom of the pane, and select *Duplicate*. > [!NOTE] -> In DataMiner Cube, it is possible to add Correlation rules that use the deprecated System Display Correlation engine. To do so, right-click in the tree view pane (or click the *More...* button at the bottom of the pane) and select *Advanced* > *Old engine* > *Add rule*. +> In DataMiner Cube, it is possible to add Correlation rules that use the deprecated System Display Correlation engine if the server is running a DataMiner version prior to 10.5.1. To do so, right-click in the tree view pane (or click the *More...* button at the bottom of the pane) and select *Advanced* > *Old engine* > *Add rule*. diff --git a/user-guide/Reference/DataMiner_Tools/SLNetClientTest_tool/SLNetClientTest_tool_diagnostic_procedures/SLNetClientTest_tracking_dma_communication.md b/user-guide/Reference/DataMiner_Tools/SLNetClientTest_tool/SLNetClientTest_tool_diagnostic_procedures/SLNetClientTest_tracking_dma_communication.md index 74907c3d5b..1648e971b9 100644 --- a/user-guide/Reference/DataMiner_Tools/SLNetClientTest_tool/SLNetClientTest_tool_diagnostic_procedures/SLNetClientTest_tracking_dma_communication.md +++ b/user-guide/Reference/DataMiner_Tools/SLNetClientTest_tool/SLNetClientTest_tool_diagnostic_procedures/SLNetClientTest_tracking_dma_communication.md @@ -20,7 +20,7 @@ To activate follow mode: 1. Select what should be followed. The following options are available: - - *Hook into Active Session*: Allows you to select a particular item to follow from the current active session, e.g. SLBrain.exe + - *Hook into Active Session*: Allows you to select a particular item to follow from the current active session, e.g. SLDataMiner.exe - *Hook into Custom Active Session*: Allows you to specify a particular connection ID diff --git a/user-guide/Reference/Skyline_DataMiner_Folder/Overview_of_the_files_found_in_the_root_folder.md b/user-guide/Reference/Skyline_DataMiner_Folder/Overview_of_the_files_found_in_the_root_folder.md index 691aac2f2b..55685c16a9 100644 --- a/user-guide/Reference/Skyline_DataMiner_Folder/Overview_of_the_files_found_in_the_root_folder.md +++ b/user-guide/Reference/Skyline_DataMiner_Folder/Overview_of_the_files_found_in_the_root_folder.md @@ -10,7 +10,7 @@ uid: Overview_of_the_files_found_in_the_root_folder | Name | Description | Synchronized? | |--|--|--| | BaseSubscriptions.xml | Base subscriptions, i.e. element subscriptions that remain open, so that the element info is cached in SLNet. | No | -| Brain.xml | Correlation rules. | Yes | +| Brain.xml | Legacy Correlation rules. (In versions prior to 10.5.1) | Yes | | ClientApps.lic | License file for client applications. No longer used. When you upgrade to a recent DataMiner version, this file is removed during the upgrade. | No | | ClusterInfo.xml | Contains the ID ranges for the views of each DMA in the cluster. | Yes | | DataMiner.lic | DataMiner license file. | No | diff --git a/user-guide/Troubleshooting/Troubleshooting_Flowcharts/Troubleshooting_Process_Identification/Troubleshooting_Process_Identification.md b/user-guide/Troubleshooting/Troubleshooting_Flowcharts/Troubleshooting_Process_Identification/Troubleshooting_Process_Identification.md index 73a56f5e4f..61fae6feff 100644 --- a/user-guide/Troubleshooting/Troubleshooting_Flowcharts/Troubleshooting_Process_Identification/Troubleshooting_Process_Identification.md +++ b/user-guide/Troubleshooting/Troubleshooting_Flowcharts/Troubleshooting_Process_Identification/Troubleshooting_Process_Identification.md @@ -51,6 +51,5 @@ uid: Troubleshooting_Process_Identification | [SLASPConnection.exe](xref:Troubleshooting_SLASPConnection_exe) | Generates legacy reports and sends reports/notifications via email. | | [SLAnalytics.exe](xref:Troubleshooting_SLAnalytics_exe) | AI-driven prediction and other DataMiner Analytics features. | | [SLHelper.exe](xref:Troubleshooting_SLHelper_exe) | Performs various small tasks. | -| SLBrain.exe | Backwards compatibility DataMiner 8.0 Correlation.
Deprecated. | | [SLScheduler.exe](xref:Troubleshooting_SLScheduler_exe) | Schedules DataMiner tasks. | | [w3wp.exe](xref:Investigating_Web_Issues) | Windows worker process of the IIS Web Server. | From 4e951f0f17da87e0a7b492046b67660ac33d47fa Mon Sep 17 00:00:00 2001 From: Wouter Demuynck Date: Tue, 19 Nov 2024 10:05:30 +0100 Subject: [PATCH 2/4] Add MR --- .../About_DataMiner_Systems/DataMiner_processes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/user-guide/Advanced_Functionality/DataMiner_Systems/About_DataMiner_Systems/DataMiner_processes.md b/user-guide/Advanced_Functionality/DataMiner_Systems/About_DataMiner_Systems/DataMiner_processes.md index 6cb3c0ace4..de24a67f8d 100644 --- a/user-guide/Advanced_Functionality/DataMiner_Systems/About_DataMiner_Systems/DataMiner_processes.md +++ b/user-guide/Advanced_Functionality/DataMiner_Systems/About_DataMiner_Systems/DataMiner_processes.md @@ -157,7 +157,7 @@ The DataMiner Automation process. The DataMiner Legacy Correlation process. > [!NOTE] -> Only available on DataMiner versions before 10.5.1. +> Only available on DataMiner versions before 10.5.1/10.6.0. > [!TIP] > See also: [DataMiner Correlation](xref:About_DMS_Correlation) From 1596e166a7c2fbf0364c146491d073a5c4216f6e Mon Sep 17 00:00:00 2001 From: Wouter Demuynck Date: Tue, 19 Nov 2024 10:08:01 +0100 Subject: [PATCH 3/4] More add MR --- .../Overview_of_the_files_found_in_the_root_folder.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/user-guide/Reference/Skyline_DataMiner_Folder/Overview_of_the_files_found_in_the_root_folder.md b/user-guide/Reference/Skyline_DataMiner_Folder/Overview_of_the_files_found_in_the_root_folder.md index 55685c16a9..1138b7f5d6 100644 --- a/user-guide/Reference/Skyline_DataMiner_Folder/Overview_of_the_files_found_in_the_root_folder.md +++ b/user-guide/Reference/Skyline_DataMiner_Folder/Overview_of_the_files_found_in_the_root_folder.md @@ -10,7 +10,7 @@ uid: Overview_of_the_files_found_in_the_root_folder | Name | Description | Synchronized? | |--|--|--| | BaseSubscriptions.xml | Base subscriptions, i.e. element subscriptions that remain open, so that the element info is cached in SLNet. | No | -| Brain.xml | Legacy Correlation rules. (In versions prior to 10.5.1) | Yes | +| Brain.xml | Legacy Correlation rules. (In versions prior to 10.5.1/10.6.0) | Yes | | ClientApps.lic | License file for client applications. No longer used. When you upgrade to a recent DataMiner version, this file is removed during the upgrade. | No | | ClusterInfo.xml | Contains the ID ranges for the views of each DMA in the cluster. | Yes | | DataMiner.lic | DataMiner license file. | No | From 83c025a736cb34cf1001b0a5bf2c142317df35df Mon Sep 17 00:00:00 2001 From: Wouter Demuynck Date: Tue, 19 Nov 2024 10:10:07 +0100 Subject: [PATCH 4/4] RTE example: use SLDMS instead of SLBrain as an example --- .../DataMiner_logging/Watchdog_logging.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/user-guide/Troubleshooting/Logging/Consulting_the_DataMiner_logs/DataMiner_logging/Watchdog_logging.md b/user-guide/Troubleshooting/Logging/Consulting_the_DataMiner_logs/DataMiner_logging/Watchdog_logging.md index 678d5aaec4..30144d6839 100644 --- a/user-guide/Troubleshooting/Logging/Consulting_the_DataMiner_logs/DataMiner_logging/Watchdog_logging.md +++ b/user-guide/Troubleshooting/Logging/Consulting_the_DataMiner_logs/DataMiner_logging/Watchdog_logging.md @@ -43,11 +43,11 @@ If the time in parentheses has elapsed twice, a full run-time error is triggered An RTE logged by SLWatchdog can for instance look like this: ```txt -2021-02-27 07:48:39 8260|>>>>>>> (320) THREAD PROBLEM : SLBrain.exe - Handle Notifications Thread -2021-02-27 07:48:39 8260|Send alarm for process SLBrain.exe (bSignaled = FALSE, bStopped = FALSE) for iCookie = 320 (RTE Count = 1) +2021-02-27 07:48:39 8260|>>>>>>> (320) THREAD PROBLEM : SLDMS.exe - NotificationThread +2021-02-27 07:48:39 8260|Send alarm for process SLDMS.exe (bSignaled = FALSE, bStopped = FALSE) for iCookie = 320 (RTE Count = 1) 2021-02-27 07:48:39 8260|** Making minidump .. -2021-02-27 07:48:48 8260|** Making minidump C:\Skyline DataMiner\Logging\MiniDump\2018_02_27 07_48_39_SLBrain.exe.zip finished. -2021-02-27 07:48:48 8260|OPEN RTE: Runtime error in process SLBrain.exe on agent MIEKED2 in Process: SLBrain.exe for Thread: Handle Notifications Thread with notificationID: 11395 +2021-02-27 07:48:48 8260|** Making minidump C:\Skyline DataMiner\Logging\MiniDump\2018_02_27 07_48_39_SLDMS.exe.zip finished. +2021-02-27 07:48:48 8260|OPEN RTE: Runtime error in process SLDMS.exe on agent MIEKED2 in Process: SLDMS.exe for Thread: NotificationThread with notificationID: 11395 ``` The "RTE Count" you can see in the example above refers to the number of processes with a distinct name that have an RTE. This counter will only increase when a process with a different name also has an RTE. If, for example, there are 5 SLProtocol processes with an RTE, the RTE Count is 1. However, if SLElement were to have an RTE as well, the RTE Count would increase to 2. The RTE Count will only go back to 0 when all threads are OK again and all processes are working as expected.