diff --git a/docs/serverless/rules/rules-ui-management.asciidoc b/docs/serverless/rules/rules-ui-management.asciidoc index e2be121fc1..130f8ed91c 100644 --- a/docs/serverless/rules/rules-ui-management.asciidoc +++ b/docs/serverless/rules/rules-ui-management.asciidoc @@ -81,7 +81,7 @@ Similarly, rules will be skipped if they can't be modified by a bulk edit. For e + [NOTE] ==== -Rule actions won't run during a {kibana-ref}/maintenance-windows.html[maintenance window]. They'll resume running after the maintenance window ends. +Rule actions won't run during a <>. They'll resume running after the maintenance window ends. ==== ** **Update rule schedules**: Update the <> and look-back times on all selected rules. ** **Apply Timeline template**: Apply a specified <> to the selected rules. You can also choose **None** to remove Timeline templates from the selected rules. @@ -177,7 +177,7 @@ If you try to export with both prebuilt and custom rules selected, only the cust The `.ndjson` file also includes any actions, connectors, and exception lists related to the exported rules. However, other configuration items require additional handling when exporting and importing rules: -* **Data views**: For rules that use a {kib} data view as a data source, the exported file contains the associated `data_view_id`, but does _not_ include any other data view configuration. To export/import between {kib} spaces, first use the {kibana-ref}/managing-saved-objects.html#managing-saved-objects-share-to-space[Saved Objects] UI (**Project settings** → **Content** → **Saved Objects**) to share the data view with the destination space. +* **Data views**: For rules that use a {kib} data view as a data source, the exported file contains the associated `data_view_id`, but does _not_ include any other data view configuration. To export/import between {kib} spaces, first use the <> UI (**Project settings** → **Stack Management** → **Saved Objects**) to share the data view with the destination space. To import into a different {stack} deployment, the destination cluster must include a data view with a matching data view ID (configured in the {kibana-ref}/data-views.html[data view's advanced settings]). Alternatively, after importing, you can manually reconfigure the rule to use an appropriate data view in the destination system. @@ -185,7 +185,7 @@ To import into a different {stack} deployment, the destination cluster must incl + [TIP] ==== -You can also use the {kibana-ref}/managing-saved-objects.html#managing-saved-objects-share-to-space[Saved Objects] UI (**Project settings** → **Content** → **Saved Objects**) to export and import necessary connectors before importing detection rules. +You can also use the <> UI (**Project settings** → **Stack Management** → **Saved Objects**) to export and import necessary connectors before importing detection rules. ==== * **Value lists**: Any value lists used for rule exceptions are _not_ included in rule exports or imports. Use the <> UI (**Rules** → **Detection rules (SIEM)** → **Manage value lists**) to export and import value lists separately.