Documents steps for deleting the user & host risk score modules (#4074)…

… (#4094) * Adds steps for deleting the host risk score module * Adds steps for deleting the user risk score module * Deletes empty lines * Apply suggestions from TW review Co-authored-by: Benjamin Ironside Goldstein <[email protected]> * Applies TW feedback * Apply suggestions from TW review Co-authored-by: Janeen Mikell Roberts <[email protected]> --------- Co-authored-by: Benjamin Ironside Goldstein <[email protected]> Co-authored-by: Janeen Mikell Roberts <[email protected]> (cherry picked from commit 29baa07) Co-authored-by: natasha-moore-elastic <[email protected]>
elastic · Oct 24, 2023 · 86576ff · 86576ff
1 parent 2eeb1da
commit 86576ff
Show file tree

Hide file tree

Showing 6 changed files with 139 additions and 3 deletions.
diff --git a/docs/experimental-features/host-risk-score.asciidoc b/docs/experimental-features/host-risk-score.asciidoc
@@ -70,6 +70,8 @@ To enable host risk score from Console in {kib}, open a browser window and enter
 
 NOTE: If there's existing content in Console, scroll to the bottom to find the output loaded. 
 
+TIP: If you receive an error message during the installation process, delete the host risk score module manually, then re-enable it. Refer to <<troubleshoot-host-risk-score, Troubleshooting>> for more information. 
+
 [[upgrade-host-risk-score]]
 [discrete]
 === Upgrade host risk score 
@@ -88,7 +90,9 @@ After this is done, you can proceed with upgrading the host risk score feature f
 * The *Host risk* tab on the Hosts page
 * The *Host risk* tab on a host's details page
 
-NOTE: After you enable or upgrade host risk score, you might get a message that says, "No host risk score data available to display." To verify that the transform that installs the host risk score module is picking up data, refer to <<verify-host-risk-score, Verify that host risk score data installed successfully>>. 
+NOTE: After you enable or upgrade host risk score, you might get a message that says, "No host risk score data available to display." To verify that the transform that installs the host risk score module is picking up data, refer to <<verify-host-risk-score, Verify that host risk score data installed successfully>>.
+
+TIP: If you receive an error message during the upgrade process, delete the host risk score module manually, and then re-enable it. Refer to <<troubleshoot-host-risk-score, Troubleshooting>> for more information. 
 
 [[analyze-host-risk-score]]
 [discrete]
@@ -156,6 +160,71 @@ The histogram shows historical changes in a particular host's risk score(s). To
 [role="screenshot"]
 image::images/data-tables.png[]
 
+[[troubleshoot-host-risk-score]]
+[discrete]
+=== Troubleshooting
+
+During the installation or upgrade process, you may receive the following error messages:
+
+* `Saved object already exists`
+* `Transform already exists`
+* `Ingest pipeline already exists`
+
+In this case, we recommend that you manually delete the host risk score module, then re-enable it. To manually delete the module:
+
+. Delete the host risk score saved objects:
+.. From the {kib} main menu, go to **Stack Management** -> **Kibana** -> **Saved Objects**.
+.. Delete the saved objects that have the `Host Risk Score - <space-id>` tag.
++
+[role="screenshot"]
+image::images/delete-hrs-saved-objects.png[Delete host risk score saved objects]
+.. Delete the `Host Risk Score - <space-id>` tag.
++
+[role="screenshot"]
+image::images/delete-hrs-tag.png[Delete host risk score tag]
+. Stop and delete the host risk score transforms. You can do this using the {kib} UI or the {ref}/stop-transform.html[Stop transform API] and {ref}/delete-transform.html[Delete transform API].
+** To delete the host risk score transforms using the {kib} UI:
+.. From the {kib} main menu, go to **Stack Management** -> **Data** -> **Transforms**.
+.. Stop the following transforms, then delete them:
+*** `ml_hostriskscore_latest_transform_<space-id>`
+*** `ml_hostriskscore_pivot_transform_<space-id>`
+** To delete the host risk score transforms using the API, run the following commands in Console:
+.. Stop and delete the latest transform:
++
+[source,console]
+----------------------------------
+POST _transform/ml_hostriskscore_latest_transform_<space-id>/_stop
+DELETE _transform/ml_hostriskscore_latest_transform_<space-id>
+----------------------------------
+.. Stop and delete the pivot transform:
++
+[source,console]
+----------------------------------
+POST _transform/ml_hostriskscore_pivot_transform_<space-id>/_stop
+DELETE _transform/ml_hostriskscore_pivot_transform_<space-id>
+----------------------------------
+. Delete the host risk score ingest pipeline. You can do this using the {kib} UI or the {ref}/delete-pipeline-api.html[Delete pipeline API].
+** To delete the host risk score ingest pipeline using the {kib} UI:
+.. From the {kib} main menu, go to **Stack Management** -> **Ingest** -> **Ingest Pipelines**.
+.. Delete the `ml_hostriskscore_ingest_pipeline_<space-id>` ingest pipeline.
+** To delete the host risk score ingest pipeline using the Delete pipeline API, run the following command in Console:
++
+[source,console]
+----------------------------------
+DELETE /_ingest/pipeline/ml_hostriskscore_ingest_pipeline_<space-id>
+----------------------------------
+. Delete the stored host risk score scripts using the {ref}/delete-stored-script-api.html[Delete stored script API]. In Console, run the following commands:
++
+[source,console]
+----------------------------------
+DELETE _scripts/ml_hostriskscore_levels_script_<space-id>
+DELETE _scripts/ml_hostriskscore_init_script_<space-id>
+DELETE _scripts/ml_hostriskscore_map_script_<space-id>
+DELETE _scripts/ml_hostriskscore_reduce_script_<space-id>
+----------------------------------
+
+After manually deleting the host risk score saved objects, transforms, ingest pipeline, and stored scripts, follow the steps to <<enable-host-risk-score, re-enable the host risk score module>>.
+
 [[verify-host-risk-score]]
 === Verify that host risk score data installed successfully (Optional)
 

diff --git a/docs/experimental-features/images/delete-hrs-saved-objects.png b/docs/experimental-features/images/delete-hrs-saved-objects.png
diff --git a/docs/experimental-features/images/delete-hrs-tag.png b/docs/experimental-features/images/delete-hrs-tag.png
diff --git a/docs/experimental-features/images/delete-urs-saved-objects.png b/docs/experimental-features/images/delete-urs-saved-objects.png
diff --git a/docs/experimental-features/images/delete-urs-tag.png b/docs/experimental-features/images/delete-urs-tag.png
diff --git a/docs/experimental-features/user-risk-score.asciidoc b/docs/experimental-features/user-risk-score.asciidoc
@@ -61,7 +61,9 @@ To enable user risk score from Console in {kib}, open a browser window and enter
 {KibanaURL}/s/{spaceID}/app/dev_tools#/console?load_from={KibanaURL}/s/{spaceID}/internal/risk_score/prebuilt_content/dev_tool/enable_user_risk_score
 ----------------------------------
 
-NOTE: If there's existing content in Console, scroll to the bottom to find the output loaded. 
+NOTE: If there's existing content in Console, scroll to the bottom to find the output loaded.
+
+TIP: If you receive an error message during the installation process, delete the user risk score module manually, and then re-enable it. Refer to <<troubleshoot-user-risk-score, Troubleshooting>> for more information. 
 
 [[upgrade-user-risk-score]]
 [discrete]
@@ -81,7 +83,9 @@ After this is done, you can proceed with upgrading the user risk score feature f
 * The *User risk* tab on the User page
 * The *User risk* tab on a user's details page
 
-NOTE: After you enable or upgrade user risk score, you might get a message that says, "No user risk score data available to display." To verify that the transform that installs the user risk score module is picking up data, refer to <<verify-user-risk-score, Verify that user risk score data installed successfully>>. 
+NOTE: After you enable or upgrade user risk score, you might get a message that says, "No user risk score data available to display." To verify that the transform that installs the user risk score module is picking up data, refer to <<verify-user-risk-score, Verify that user risk score data installed successfully>>.
+
+TIP: If you receive an error message during the installation process, delete the user risk score module manually, and then re-enable it. Refer to <<troubleshoot-user-risk-score, Troubleshooting>> for more information.
 
 [[view-user-risk-score]]
 [discrete]
@@ -136,6 +140,69 @@ The data tables beneath the histogram display associated rules, users, and MITRE
 [role="screenshot"]
 image::images/dashboard.gif[User risk score dashboard]
 
+[[troubleshoot-user-risk-score]]
+[discrete]
+=== Troubleshooting
+
+During the installation or upgrade process, you may receive the following error messages:
+
+* `Saved object already exists`
+* `Transform already exists`
+* `Ingest pipeline already exists`
+
+In this case, we recommend that you manually delete the user risk score module, and then re-enable it. To manually delete the module:
+
+. Delete the user risk score saved objects:
+.. From the {kib} main menu, go to **Stack Management** -> **Kibana** -> **Saved Objects**.
+.. Delete the saved objects that have the `User Risk Score - <space-id>` tag.
++
+[role="screenshot"]
+image::images/delete-urs-saved-objects.png[Delete user risk score saved objects]
+.. Delete the `User Risk Score - <space-id>` tag.
++
+[role="screenshot"]
+image::images/delete-urs-tag.png[Delete user risk score tag]
+. Stop and delete the user risk score transforms. You can do this using the {kib} UI or the {ref}/stop-transform.html[Stop transform API] and {ref}/delete-transform.html[Delete transform API].
+** To delete the user risk score transforms using the {kib} UI:
+.. From the {kib} main menu, go to **Stack Management** -> **Data** -> **Transforms**.
+.. Stop the following transforms, then delete them:
+*** `ml_userriskscore_latest_transform_<space-id>`
+*** `ml_userriskscore_pivot_transform_<space-id>`
+** To delete the user risk score transforms using the API, run the following commands in Console:
+.. Stop and delete the latest transform:
++
+[source,console]
+----------------------------------
+POST _transform/ml_userriskscore_latest_transform_<space-id>/_stop
+DELETE _transform/ml_userriskscore_latest_transform_<space-id>
+----------------------------------
+.. Stop and delete the pivot transform:
++
+[source,console]
+----------------------------------
+POST _transform/ml_userriskscore_pivot_transform_<space-id>/_stop
+DELETE _transform/ml_userriskscore_pivot_transform_<space-id>
+----------------------------------
+. Delete the user risk score ingest pipeline. You can do this using the {kib} UI or the {ref}/delete-pipeline-api.html[Delete pipeline API].
+** To delete the user risk score ingest pipeline using the {kib} UI:
+.. From the {kib} main menu, go to **Stack Management** -> **Ingest** -> **Ingest Pipelines**.
+.. Delete the `ml_userriskscore_ingest_pipeline_<space-id>` ingest pipeline.
+** To delete the user risk score ingest pipeline using the Delete pipeline API, run the following command in Console:
++
+[source,console]
+----------------------------------
+DELETE /_ingest/pipeline/ml_userriskscore_ingest_pipeline_<space-id>
+----------------------------------
+. Delete the stored user risk score scripts using the {ref}/delete-stored-script-api.html[Delete stored script API]. In Console, run the following commands:
++
+[source,console]
+----------------------------------
+DELETE _scripts/ml_userriskscore_levels_script_<space-id>
+DELETE _scripts/ml_userriskscore_map_script_<space-id>
+DELETE _scripts/ml_userriskscore_reduce_script_<space-id>
+----------------------------------
+
+After manually deleting the user risk score saved objects, transforms, ingest pipeline, and stored scripts, follow the steps to <<deploy-user-risk-score, re-enable the user risk score module>>.
 
 [[verify-user-risk-score]]
 === Verify that user risk score data installed successfully (Optional)