From 554f4153427978e2dcfa26ac28906c30d817fe9b Mon Sep 17 00:00:00 2001 From: Marieke Goethals Date: Wed, 14 Jan 2026 11:28:05 +0100 Subject: [PATCH 1/2] RN 44201 + 44435 Note that I did not include version info as this feature already wasn't supported for STaaS, even though it was shown in Cube. Also included info to clarify when booking migration option is shown. --- .../storage_per_DMA/Configuring_DataMiner_Indexing.md | 11 +++++------ .../Applying_alarm_filters_in_the_Alarm_Console.md | 4 ++-- 2 files changed, 7 insertions(+), 8 deletions(-) diff --git a/dataminer/Administrator_guide/Databases/Indexing_database/Elasticsearch/storage_per_DMA/Configuring_DataMiner_Indexing.md b/dataminer/Administrator_guide/Databases/Indexing_database/Elasticsearch/storage_per_DMA/Configuring_DataMiner_Indexing.md index dddd72dfe9..a34b30c8a2 100644 --- a/dataminer/Administrator_guide/Databases/Indexing_database/Elasticsearch/storage_per_DMA/Configuring_DataMiner_Indexing.md +++ b/dataminer/Administrator_guide/Databases/Indexing_database/Elasticsearch/storage_per_DMA/Configuring_DataMiner_Indexing.md @@ -4,7 +4,9 @@ uid: Configuring_DataMiner_Indexing # Configuring indexing settings in DataMiner Cube -The indexing settings in System Center determine which information is stored in the indexing database. To configure these settings, go to *System Center* > *Search & Indexing*. +The indexing settings in System Center determine which information is stored in the indexing database of a [dedicated clustered storage](xref:Dedicated_clustered_storage) setup. For systems using [STaaS](xref:STaaS), this configuration is not used. + +To configure these settings, go to *System Center* > *Search & Indexing*. > [!TIP] > @@ -15,10 +17,7 @@ The following settings are available: - *Enable indexing on alarms:* Enables indexing of alarms. If this option is not enabled, the enhanced search options in the Alarm Console are not available. -- *Migrate booking data to Indexing Engine*: Starts a wizard that allows you to migrate booking data from the Cassandra database to the indexing database. Only displayed in case booking data have not been migrated yet. - - > [!NOTE] - > If you are using a [DaaS system](xref:Creating_a_DMS_in_the_cloud), Indexing Engine settings cannot be customized. As such, from DataMiner 10.3.0 [CU15]/10.4.0 [CU3]/10.4.6 onwards, the Indexing Engine settings are no longer available for DaaS. +- *Migrate booking data to Indexing Engine*: Prior to DataMiner 10.4, this allows you to migrate booking data from the Cassandra database to the indexing database, if this has not been done yet. This migration must be done before you can upgrade to DataMiner 10.4 or higher. Please note the following regarding the migration of booking data: @@ -34,7 +33,7 @@ The following settings are available: > > - The indexing configuration is saved in the file *Indexing.xml* in the folder `C:\Skyline DataMiner\Database`. > - To include booking data from the indexing database in a custom backup, select *Include SRM in backup* in the content tab of the *Backup* page. See [Configuring the DataMiner backups](xref:Backing_up_a_DataMiner_Agent_in_DataMiner_Cube#configuring-the-dataminer-backups). -> - Resources are not automatically migrated to the indexing database as well. For more information on how to migrate these, see [Migrating SRM resources to the indexing database](xref:Resources_migration_to_elastic). +> - Resources and profiles are not automatically migrated to the indexing database as well. For more information on how to migrate these, see [Migrating SRM resources to the indexing database](xref:Resources_migration_to_elastic) and [Migrating SRM profiles to the indexing database](xref:Profile_migration_to_elastic). > [!TIP] > See also: [Indexing database settings](xref:DB_xml#indexing-database-settings) diff --git a/dataminer/Operator_guide/Alarms/Working_with_alarms/Working_with_the_Alarm_Console/Applying_alarm_filters_in_the_Alarm_Console.md b/dataminer/Operator_guide/Alarms/Working_with_alarms/Working_with_the_Alarm_Console/Applying_alarm_filters_in_the_Alarm_Console.md index a721b44c91..1f44c93c6b 100644 --- a/dataminer/Operator_guide/Alarms/Working_with_alarms/Working_with_the_Alarm_Console/Applying_alarm_filters_in_the_Alarm_Console.md +++ b/dataminer/Operator_guide/Alarms/Working_with_alarms/Working_with_the_Alarm_Console/Applying_alarm_filters_in_the_Alarm_Console.md @@ -22,7 +22,7 @@ This filter box can be used in different ways: - *Exclude \[highlighted text\] in filter*: This option can only be used on an item that is not yet in the filter, and adds a negative filter for this item. This is the equivalent to adding an exclamation mark in front of an item when you type text in the filter. - - *Search for \[selected text\] in new tab*: This option opens a new *Search alarms* tab in the Alarm Console, in which you can search through alarms using this filter. This option is only available on a DMA with [indexing database](xref:Indexing_Database). + - *Search for \[selected text\] in new tab*: This option opens a new *Search alarms* tab in the Alarm Console, in which you can search through alarms using this filter. This option is only available if the DMS uses [self-managed storage with indexing database](xref:Indexing_Database). - *Copy \[highlighted text\]* @@ -97,7 +97,7 @@ To add such a filtered tab page: ## Creating a search tab in the Alarm Console -When you are connected to a DMA with [indexing database](xref:Indexing_Database), the Alarm Console provides an additional option to create a dynamic search tab: +When you are connected to a DMS with [self-managed storage with indexing database](xref:Indexing_Database), the Alarm Console provides an additional option to create a dynamic search tab: 1. Click the *+* symbol in the header of the Alarm Console to open a new tab. From 033d444ff2235abf1802ccd434e9d130f39c4ed1 Mon Sep 17 00:00:00 2001 From: Marieke Goethals Date: Wed, 14 Jan 2026 16:00:24 +0100 Subject: [PATCH 2/2] Update Configuring_DataMiner_Indexing.md --- .../storage_per_DMA/Configuring_DataMiner_Indexing.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/dataminer/Administrator_guide/Databases/Indexing_database/Elasticsearch/storage_per_DMA/Configuring_DataMiner_Indexing.md b/dataminer/Administrator_guide/Databases/Indexing_database/Elasticsearch/storage_per_DMA/Configuring_DataMiner_Indexing.md index a34b30c8a2..5dae0374fa 100644 --- a/dataminer/Administrator_guide/Databases/Indexing_database/Elasticsearch/storage_per_DMA/Configuring_DataMiner_Indexing.md +++ b/dataminer/Administrator_guide/Databases/Indexing_database/Elasticsearch/storage_per_DMA/Configuring_DataMiner_Indexing.md @@ -4,7 +4,7 @@ uid: Configuring_DataMiner_Indexing # Configuring indexing settings in DataMiner Cube -The indexing settings in System Center determine which information is stored in the indexing database of a [dedicated clustered storage](xref:Dedicated_clustered_storage) setup. For systems using [STaaS](xref:STaaS), this configuration is not used. +The indexing settings in System Center determine which information is stored in the indexing database of a [dedicated clustered storage](xref:Dedicated_clustered_storage) setup. To configure these settings, go to *System Center* > *Search & Indexing*. @@ -15,7 +15,7 @@ To configure these settings, go to *System Center* > *Search & Indexing*. The following settings are available: -- *Enable indexing on alarms:* Enables indexing of alarms. If this option is not enabled, the enhanced search options in the Alarm Console are not available. +- *Enable indexing on alarms:* Enables indexing of alarms. If this option is not enabled, the enhanced search options in the Alarm Console are not available. For systems using [STaaS](xref:STaaS) or [dedicated clustered storage](xref:Dedicated_clustered_storage), this setting is not used. - *Migrate booking data to Indexing Engine*: Prior to DataMiner 10.4, this allows you to migrate booking data from the Cassandra database to the indexing database, if this has not been done yet. This migration must be done before you can upgrade to DataMiner 10.4 or higher.