Skip to content

Commit 86717fd

Browse files
mergify[bot]nastasha-solomongithub-actions[bot]
authored
[8.14] [DE Team][BUG]: Missing info in req docs for detections (backport #5708) (#5776)
* [DE Team][BUG]: Missing info in req docs for detections (#5708) * First draft * removed extra hash * Removed comments * Changed page name * Adds space req to Serverless data view docs (cherry picked from commit 11535f0) # Conflicts: # docs/serverless/explore/data-views-in-sec.mdx * Delete docs/serverless directory and its contents --------- Co-authored-by: Nastasha Solomon <[email protected]> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
1 parent ccd89d0 commit 86717fd

File tree

2 files changed

+6
-3
lines changed

2 files changed

+6
-3
lines changed

docs/detections/detections-req.asciidoc

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,8 @@ and restarting {kib}, you must restart all detection rules.
3636
[discrete]
3737
[[enable-detections-ui]]
3838
== Enable and access detections
39-
To use the Detections feature, it must be enabled and your role must have access to rules and alerts. If your role does not have the cluster and index privileges needed to enable this feature, you can request someone who has these privileges to visit your Kibana space, which will turn it on for you. The following table describes the required privileges to access the Detections page, including rules and alerts.
39+
40+
To use the Detections feature, it must be enabled, your role must have access to rules and alerts, and your {kib} space must have **Data View Management** {kibana-ref}/xpack-spaces.html#spaces-control-feature-visibility[feature visibility]. If your role does not have the cluster and index privileges needed to enable this feature, you can request someone who has these privileges to visit your Kibana space, which will turn it on for you. The following table describes the required privileges to access the Detections feature, including rules and alerts.
4041

4142
NOTE: For instructions about using Machine Learning jobs and rules, refer to <<ml-requirements, Machine learning job and rule requirements>>.
4243

@@ -65,7 +66,7 @@ a|The `manage`, `write`,`read`, and `view_index_metadata` index privileges for t
6566

6667
|Enable the Detections feature in all Kibana spaces
6768

68-
*NOTE*: To turn on the Detections feature, visit the Detections page for each appropriate Kibana space.
69+
*NOTE*: To turn on the Detections feature, visit the Rules and Alerts pages for each appropriate Kibana space.
6970

7071
|The `manage` privilege
7172
a|The `manage`, `write`,`read`, and `view_index_metadata` index privileges for the following system indices and data streams:

docs/getting-started/data-views-in-sec.asciidoc

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,8 @@ NOTE: You cannot update the data view for the Alerts page. This includes referen
3535

3636
The default {data-source} is defined by the `securitySolution:defaultIndex` setting, which you can modify in {kib}'s advanced settings (**Stack Management** > **Advanced Settings** > **Security Solution**). To learn more about this setting, including its default value, refer to {security-guide}/advanced-settings.html#update-sec-indices[Advanced settings].
3737

38-
The first time a user visits {elastic-sec} within a given {kib} {kibana-ref}/xpack-spaces.html[space], the default {data-source} generates in that space and becomes active.
38+
The first time a user visits {elastic-sec} within a given {kib} {kibana-ref}/xpack-spaces.html[space], the default {data-source} generates in that space and becomes active.
39+
40+
NOTE: Your {kib} space must have **Data View Management** {kibana-ref}/xpack-spaces.html#spaces-control-feature-visibility[feature visibility] setting enabled for the default {data-source} to generate and become active in your space.
3941

4042
If you delete the active {data-source} when there are no other defined {data-sources}, the default {data-source} will regenerate and become active upon refreshing any {elastic-sec} page in the space.

0 commit comments

Comments
 (0)