From 06e74d41daeb41e5faa8ab9b05fa7317ffb5b5b7 Mon Sep 17 00:00:00 2001 From: Joe Peeples Date: Fri, 19 Jul 2024 08:30:48 -0400 Subject: [PATCH] (Doc+) Alerts UI cannot be CCS [serverless] + bonus fixes (#5582) * Add admonition to serverless Serverless follow up to https://github.com/elastic/security-docs/pull/5513 * Update serverless to match ESS Serverless follow up to https://github.com/elastic/security-docs/pull/4695 * Fix URL variable/attribute Should use `kibana-ref` instead of apm-app-ref since this has nothing to do with APM * No-op change to trigger build (i hope) (cherry picked from commit 9e7d734ac6c92a485c01319db6ba92136f56e52a) # Conflicts: # docs/serverless/explore/data-views-in-sec.mdx --- .../data-views-in-sec.asciidoc | 7 ++- docs/serverless/explore/data-views-in-sec.mdx | 51 +++++++++++++++++++ 2 files changed, 54 insertions(+), 4 deletions(-) create mode 100644 docs/serverless/explore/data-views-in-sec.mdx diff --git a/docs/getting-started/data-views-in-sec.asciidoc b/docs/getting-started/data-views-in-sec.asciidoc index 7b0d75074b..9d3784ca52 100644 --- a/docs/getting-started/data-views-in-sec.asciidoc +++ b/docs/getting-started/data-views-in-sec.asciidoc @@ -10,8 +10,7 @@ IMPORTANT: Custom indices are not included in the <>. -To learn how to modify, create, or delete another {data-source} refer to {apm-app-ref}/data-views.html[{kib} {data-sources-cap}]. +To learn how to modify, create, or delete another {data-source} refer to {kibana-ref}/data-views.html[{kib} {data-sources-cap}]. You can also temporarily modify the active {data-source} from the *{data-source-cap}* menu by clicking *Advanced options*, then adding or removing index patterns. @@ -36,6 +35,6 @@ NOTE: You cannot update the data view for the Alerts page. This includes referen 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]. -The first time a user visits {elastic-sec} within a given {kib} {apm-app-ref}/xpack-spaces.html[space], the default {data-source} generates in that space and becomes active. +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. 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. diff --git a/docs/serverless/explore/data-views-in-sec.mdx b/docs/serverless/explore/data-views-in-sec.mdx new file mode 100644 index 0000000000..827c188512 --- /dev/null +++ b/docs/serverless/explore/data-views-in-sec.mdx @@ -0,0 +1,51 @@ +--- +slug: /serverless/security/data-views-in-sec +title: ((data-sources-cap)) in Elastic Security +description: Use data views to control what data displays on ((elastic-sec)) pages with event or alert data. +tags: [ 'serverless', 'security', 'reference', 'manage' ] +status: in review +--- + + +
+ +((data-sources-cap)) determine what data displays on ((elastic-sec)) pages with event or alert data. +((data-sources-cap)) are defined by the index patterns they include. +Only data from ((es)) [indices](((ref))/documents-indices.html), [data streams](((ref))/data-streams.html), or [index aliases](((ref))/alias.html) specified in the active ((data-source)) will appear. + + +Custom indices are not included in the default ((data-source)). Modify it or create a custom ((data-source)) to include custom indices. + + +## Switch to another ((data-source)) + +You can tell which ((data-source)) is active by clicking the **((data-source-cap))** menu at the upper right of ((elastic-sec)) pages that display event or alert data, such as Overview, Alerts, Timelines, or Hosts. +To switch to another ((data-source)), click **Choose ((data-source))**, select one of the options, and click **Save**. + +![image highlighting how to open the data view selection menu](../images/data-views-in-sec/-getting-started-dataview-button-highlighted.png) + +## Create or modify a ((data-source)) + +To learn how to modify the default **Security Default Data View**, refer to . + +To learn how to modify, create, or delete another ((data-source)) refer to [((data-sources-cap))](((kibana-ref))/data-views.html). + +You can also temporarily modify the active ((data-source)) from the **((data-source-cap))** menu by clicking **Advanced options**, then adding or removing index patterns. + +![video showing how to filter the active data view](../images/data-views-in-sec/-getting-started-dataview-filter-example.gif) + +This only allows you to add index patterns that match indices that currently contain data (other index patterns are unavailable). Note that any changes made are saved in the current browser window and won't persist if you open a new tab. + + + You cannot update the data view for the Alerts page. This includes referencing a cross-cluster search (CCS) data view or any other data view. The Alerts page always shows data from `.alerts-security.alerts-default`. + + +
+ +## The default ((data-source)) + +The default ((data-source)) is defined by the `securitySolution:defaultIndex` setting, which you can modify in your project's advanced settings{/* path to be updated: (**Stack Management** → **Advanced Settings** → **Security Solution**) */}. To learn more about this setting, including its default value, refer to ). + +The first time a user visits ((elastic-sec)){/* within a given ((kib)) [space](((kibana-ref))/xpack-spaces.html)*/}, the default ((data-source)) generates{/* in that space*/} and becomes active. + +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*/}.