diff --git a/deploy-manage/api-keys/elasticsearch-api-keys.md b/deploy-manage/api-keys/elasticsearch-api-keys.md index 1340d4d8b2..772513febf 100644 --- a/deploy-manage/api-keys/elasticsearch-api-keys.md +++ b/deploy-manage/api-keys/elasticsearch-api-keys.md @@ -15,7 +15,7 @@ You can use {{kib}} to manage your different API keys: * Cross-cluster API key: allows other clusters to connect to this cluster. * Managed API key: created and managed by Kibana to run background tasks. -To manage API keys, go to the **API Keys** management page using the navigation menu or the [global search field](../../get-started/the-stack.md#kibana-navigation-search). +To manage API keys, go to the **API Keys** management page using the navigation menu or the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md). ![API Keys UI](../../images/kibana-api-keys.png "") @@ -28,12 +28,12 @@ To manage API keys, go to the **API Keys** management page using the navigation * To create or update a **cross-cluster API key**, you must have the `manage_security` privilege and an Enterprise license. * To have a read-only view on the API keys, you must have access to the page and the `read_security` cluster privilege. -To manage roles, go to the **Roles** management page using the navigation menu or the [global search field](../../get-started/the-stack.md#kibana-navigation-search), or use the [role APIs](https://www.elastic.co/docs/api/doc/kibana/group/endpoint-roles). +To manage roles, go to the **Roles** management page using the navigation menu or the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md), or use the [role APIs](https://www.elastic.co/docs/api/doc/kibana/group/endpoint-roles). ## Create an API key [create-api-key] -To create an API key, go to the **API Keys** management page using the navigation menu or the [global search field](../../get-started/the-stack.md#kibana-navigation-search), and select **Create API key**. +To create an API key, go to the **API Keys** management page using the navigation menu or the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md), and select **Create API key**. ![Create API Key UI](../../images/kibana-create-ccr-api-key.png "") @@ -44,7 +44,7 @@ Refer to the [create cross-cluster API key](https://www.elastic.co/guide/en/elas ## Update an API key [udpate-api-key] -To update an API key, go to the **API Keys** management page using the navigation menu or the [global search field](../../get-started/the-stack.md#kibana-navigation-search), and then click on the name of the key. You cannot update the name or the type of API key. +To update an API key, go to the **API Keys** management page using the navigation menu or the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md), and then click on the name of the key. You cannot update the name or the type of API key. Refer to the [update API key](https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-update-api-key.html) documentation to learn more about updating user API keys. diff --git a/deploy-manage/deploy/elastic-cloud/create-an-elastic-cloud-hosted-deployment.md b/deploy-manage/deploy/elastic-cloud/create-an-elastic-cloud-hosted-deployment.md index 76cefa9920..189e45bff7 100644 --- a/deploy-manage/deploy/elastic-cloud/create-an-elastic-cloud-hosted-deployment.md +++ b/deploy-manage/deploy/elastic-cloud/create-an-elastic-cloud-hosted-deployment.md @@ -48,7 +48,7 @@ Once you are on the **Create deployment** page, you can create the deployment wi :::: 3. Select **Create deployment**. It takes a few minutes before your deployment gets created. While waiting, you are prompted to save the admin credentials for your deployment which provides you with superuser access to Elasticsearch. Keep these credentials safe as they are shown only once. These credentials also help you [add data using Kibana](../../../manage-data/ingest.md). If you need to refresh these credentials, you can [reset the password](../../users-roles/cluster-or-deployment-auth/built-in-users.md). -4. Once the deployment is ready, select **Continue** to open the deployment’s main page. From here, you can start [ingesting data](../../../manage-data/ingest.md) or simply [try a sample data](../../../explore-analyze/overview/kibana-quickstart.md#gs-get-data-into-kibana) set to get started. +4. Once the deployment is ready, select **Continue** to open the deployment’s main page. From here, you can start [ingesting data](../../../manage-data/ingest.md) or simply [try a sample data](../../../explore-analyze/index.md#gs-get-data-into-kibana) set to get started. At any time, you can manage and [adjust the configuration](configure.md) of your deployment to your needs, add extra layers of [security](../../users-roles/cluster-or-deployment-auth.md), or (highly recommended) set up [health monitoring](../../monitor/stack-monitoring.md). diff --git a/deploy-manage/license/manage-your-license-in-self-managed-cluster.md b/deploy-manage/license/manage-your-license-in-self-managed-cluster.md index 55a7db4613..ad437e1717 100644 --- a/deploy-manage/license/manage-your-license-in-self-managed-cluster.md +++ b/deploy-manage/license/manage-your-license-in-self-managed-cluster.md @@ -9,14 +9,14 @@ By default, new installations have a Basic license that never expires. For the f To explore all of the available solutions and features, start a 30-day free trial. You can activate a trial subscription once per major product version. If you need more than 30 days to complete your evaluation, request an extended trial at {{extendtrial}}. -To view the status of your license, start a trial, or install a new license, go to the **License Management** page using the navigation menu or the [global search field](../../get-started/the-stack.md#kibana-navigation-search). +To view the status of your license, start a trial, or install a new license, go to the **License Management** page using the navigation menu or the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md). ## Required permissions [_required_permissions_3] The `manage` cluster privilege is required to access **License Management**. -To add the privilege, go to the **Roles** management page using the navigation menu or the [global search field](../../get-started/the-stack.md#kibana-navigation-search). +To add the privilege, go to the **Roles** management page using the navigation menu or the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md). ## License expiration [license-expiration] diff --git a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md index bc40489f33..79d59b7427 100644 --- a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md +++ b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md @@ -59,7 +59,7 @@ If you use a separate monitoring cluster to store the monitoring data, it is str If the Elastic {{security-features}} are enabled, log in. -7. Go to the **Stack Monitoring** page using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +7. Go to the **Stack Monitoring** page using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). If data collection is disabled, you are prompted to turn on data collection. If {{es}} {security-features} are enabled, you must have `manage` cluster privileges to turn on data collection. diff --git a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-legacy.md b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-legacy.md index 480e74b7ba..739824d1c1 100644 --- a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-legacy.md +++ b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-legacy.md @@ -42,7 +42,7 @@ To learn about monitoring in general, see [Monitor a cluster](../../monitor.md). If {{security-features}} are enabled, log in. - 2. Go to the **Stack Monitoring** page using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). If data collection is disabled, you are prompted to turn it on. + 2. Go to the **Stack Monitoring** page using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). If data collection is disabled, you are prompted to turn it on. * From the Console or command line, set `xpack.monitoring.collection.enabled` to `true` on the production cluster.
diff --git a/deploy-manage/tools/cross-cluster-replication/ccr-getting-started-prerequisites.md b/deploy-manage/tools/cross-cluster-replication/ccr-getting-started-prerequisites.md index 4453460fc6..c7c4b3731c 100644 --- a/deploy-manage/tools/cross-cluster-replication/ccr-getting-started-prerequisites.md +++ b/deploy-manage/tools/cross-cluster-replication/ccr-getting-started-prerequisites.md @@ -9,6 +9,6 @@ To complete this tutorial, you need: * The `manage` cluster privilege on the local cluster. * A license on both clusters that includes {{ccr}}. [Activate a free 30-day trial](../../license/manage-your-license-in-self-managed-cluster.md). -* An index on the remote cluster that contains the data you want to replicate. This tutorial uses the sample eCommerce orders data set. [Load sample data](../../../explore-analyze/overview/kibana-quickstart.md#gs-get-data-into-kibana). +* An index on the remote cluster that contains the data you want to replicate. This tutorial uses the sample eCommerce orders data set. [Load sample data](../../../explore-analyze/index.md#gs-get-data-into-kibana). * In the local cluster, all nodes with the `master` [node role](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html#node-roles) must also have the [`remote_cluster_client`](../../distributed-architecture/clusters-nodes-shards/node-roles.md#remote-node) role. The local cluster must also have at least one node with both a data role and the [`remote_cluster_client`](../../distributed-architecture/clusters-nodes-shards/node-roles.md#remote-node) role. Individual tasks for coordinating replication scale based on the number of data nodes with the `remote_cluster_client` role in the local cluster. diff --git a/deploy-manage/users-roles.md b/deploy-manage/users-roles.md index 6e47818a68..7f7a88511e 100644 --- a/deploy-manage/users-roles.md +++ b/deploy-manage/users-roles.md @@ -9,7 +9,7 @@ mapped_pages: # Manage users and roles [project-settings-access] -Go to **Project settings**, then ** Management** to manage your indices, data views, saved objects, settings, and more. You can also open Management by using the [global search field](../explore-analyze/overview/kibana-quickstart.md#_finding_your_apps_and_objects). +Go to **Project settings**, then ** Management** to manage your indices, data views, saved objects, settings, and more. You can also open Management by using the [global search field](../explore-analyze/find-and-organize/find-apps-and-objects.md). Access to individual features is governed by Elastic user roles. Consult your administrator if you do not have the appropriate access. To learn more about roles, refer to [Assign user roles and privileges](users-roles/cloud-organization/manage-users.md#general-assign-user-roles). diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/quickstart.md b/deploy-manage/users-roles/cluster-or-deployment-auth/quickstart.md index d271737da3..e17ef6aced 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/quickstart.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/quickstart.md @@ -55,7 +55,7 @@ Let’s work through an example together. Consider a marketing analyst who wants Create a Marketing space for your marketing analysts to use. -1. Go to the **Spaces** management page using the navigation menu or the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Go to the **Spaces** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Create a space**. 3. Give this space a unique name. For example: `Marketing`. 4. Click **Create space**. @@ -78,7 +78,7 @@ To effectively use dashboards, create a role that describes the privileges you w To create the role: -1. Go to the **Roles** management page using the navigation menu or the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Go to the **Roles** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Create role**. 3. Give this role a unique name. For example: `marketing_dashboards_role`. 4. For this example, you want to store all marketing data in the `acme-marketing-*` set of indices. To grant this access, locate the **Index privileges** section and enter: diff --git a/explore-analyze/aggregations/tutorial-analyze-ecommerce-data-with-aggregations-using-query-dsl.md b/explore-analyze/aggregations/tutorial-analyze-ecommerce-data-with-aggregations-using-query-dsl.md index 65a31dfee2..71b76a69b7 100644 --- a/explore-analyze/aggregations/tutorial-analyze-ecommerce-data-with-aggregations-using-query-dsl.md +++ b/explore-analyze/aggregations/tutorial-analyze-ecommerce-data-with-aggregations-using-query-dsl.md @@ -31,7 +31,7 @@ You’ll need: curl -fsSL https://elastic.co/start-local | sh ``` -2. The [sample eCommerce data](../overview/kibana-quickstart.md#gs-get-data-into-kibana) loaded into {{es}}. To load sample data follow these steps in your UI: +2. The [sample eCommerce data](../index.md#gs-get-data-into-kibana) loaded into {{es}}. To load sample data follow these steps in your UI: * Open the **Integrations** pages by searching in the global search field. * Search for `sample data` in the **Integrations** search field. diff --git a/explore-analyze/alerts-cases/alerts/create-manage-rules.md b/explore-analyze/alerts-cases/alerts/create-manage-rules.md index c40d107c71..93d31c6864 100644 --- a/explore-analyze/alerts-cases/alerts/create-manage-rules.md +++ b/explore-analyze/alerts-cases/alerts/create-manage-rules.md @@ -7,7 +7,7 @@ mapped_pages: The **{{stack-manage-app}}** > **{{rules-ui}}** UI provides a cross-app view of alerting. Different {{kib}} apps like [**{{observability}}**](../../../solutions/observability/incident-management/alerting.md), [**Security**](https://www.elastic.co/guide/en/security/current/prebuilt-rules.html), [**Maps**](geo-alerting.md) and [**{{ml-app}}**](../../machine-learning/machine-learning-in-kibana.md) can offer their own rules. -You can find **Rules** in **Stack Management** > **Alerts and insights** > **Rules** in {{kib}} or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +You can find **Rules** in **Stack Management** > **Alerts and insights** > **Rules** in {{kib}} or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). ![Rules page navigation](../../../images/kibana-stack-management-rules.png "") diff --git a/explore-analyze/dashboards/create-dashboard-of-panels-with-ecommerce-data.md b/explore-analyze/dashboards/create-dashboard-of-panels-with-ecommerce-data.md index 74dd207c84..3007a3f9d2 100644 --- a/explore-analyze/dashboards/create-dashboard-of-panels-with-ecommerce-data.md +++ b/explore-analyze/dashboards/create-dashboard-of-panels-with-ecommerce-data.md @@ -14,14 +14,12 @@ When you’re done, you’ll have a complete overview of the sample web logs dat :class: screenshot ::: -Before you begin, you should be familiar with the [*{{kib}} concepts*](../overview/kibana-quickstart.md). - ## Add the data and create the dashboard [add-the-data-and-create-the-dashboard-advanced] Add the sample eCommerce data, and create and set up the dashboard. -1. [Install the eCommerce sample data set](../overview/kibana-quickstart.md#gs-get-data-into-kibana). +1. [Install the eCommerce sample data set](../index.md#gs-get-data-into-kibana). 2. Go to **Dashboards**. 3. On the **Dashboards** page, click **Create dashboard**. diff --git a/explore-analyze/dashboards/create-dashboard-of-panels-with-web-server-data.md b/explore-analyze/dashboards/create-dashboard-of-panels-with-web-server-data.md index 6b7419ee4c..d5e767feb3 100644 --- a/explore-analyze/dashboards/create-dashboard-of-panels-with-web-server-data.md +++ b/explore-analyze/dashboards/create-dashboard-of-panels-with-web-server-data.md @@ -14,14 +14,12 @@ When you’re done, you’ll have a complete overview of the sample web logs dat :class: screenshot ::: -Before you begin, you should be familiar with the [*{{kib}} concepts*](../overview/kibana-quickstart.md). - ## Add the data and create the dashboard [add-the-data-and-create-the-dashboard] Add the sample web logs data, and create and set up the dashboard. -1. [Install the web logs sample data set](../overview/kibana-quickstart.md#gs-get-data-into-kibana). +1. [Install the web logs sample data set](../index.md#gs-get-data-into-kibana). 2. Go to **Dashboards**. 3. Click **Create dashboard**. 4. Set the [time filter](../query-filter/filtering.md) to **Last 90 days**. diff --git a/explore-analyze/dashboards/drilldowns.md b/explore-analyze/dashboards/drilldowns.md index 4afe8a9838..76309bd31d 100644 --- a/explore-analyze/dashboards/drilldowns.md +++ b/explore-analyze/dashboards/drilldowns.md @@ -37,7 +37,7 @@ The panels you create using the following editors support dashboard drilldowns: ### Create and set up the dashboards you want to connect [_create_and_set_up_the_dashboards_you_want_to_connect] -Use the [**Sample web logs**](../overview/kibana-quickstart.md#gs-get-data-into-kibana) data to create a dashboard and add panels, then set a search and filter on the **[Logs] Web Traffic** dashboard. +Use the [**Sample web logs**](../index.md#gs-get-data-into-kibana) data to create a dashboard and add panels, then set a search and filter on the **[Logs] Web Traffic** dashboard. 1. Add the **Sample web logs** data. 2. Create a new dashboard, click **Add from Library**, then add the following panels: @@ -92,7 +92,7 @@ For example, **Single click** has `{{event.value}}` and **Range selection** has For example, if you have a dashboard that shows data from a Github repository, you can create a URL drilldown that opens Github from the dashboard panel. -1. Add the [**Sample web logs**](../overview/kibana-quickstart.md#gs-get-data-into-kibana) data. +1. Add the [**Sample web logs**](../index.md#gs-get-data-into-kibana) data. 2. Open the **[Logs] Web Traffic** dashboard. 3. In the toolbar, click **Edit**. 4. Create a donut chart @@ -144,7 +144,7 @@ Discover drilldowns are supported only by **Lens** panels. To open all of the ** ### Create the Discover drilldown [_create_the_discover_drilldown] -Create a drilldown that opens **Discover** from the [**Sample web logs**](../overview/kibana-quickstart.md#gs-get-data-into-kibana) data **[Logs] Web Traffic** dashboard. +Create a drilldown that opens **Discover** from the [**Sample web logs**](../index.md#gs-get-data-into-kibana) data **[Logs] Web Traffic** dashboard. 1. Click **Edit**, open the panel menu for the **[Logs] Bytes distribution** bar vertical stacked chart, then select **Create drilldown**. 2. Click **Open in Discover**. diff --git a/explore-analyze/dashboards/tutorials.md b/explore-analyze/dashboards/tutorials.md index 928a9d2442..81ca7ce5a9 100644 --- a/explore-analyze/dashboards/tutorials.md +++ b/explore-analyze/dashboards/tutorials.md @@ -7,7 +7,7 @@ mapped_pages: Learn more about building dashboards and creating visualizations with the following tutorials. -These tutorials use [sample data](../overview/kibana-quickstart.md#gs-get-data-into-kibana) available in {{kib}} as a way to get started more easily, but you can apply and adapt these instructions to your own data as well. +These tutorials use [sample data](../index.md#gs-get-data-into-kibana) available in {{kib}} as a way to get started more easily, but you can apply and adapt these instructions to your own data as well. diff --git a/explore-analyze/dashboards/using.md b/explore-analyze/dashboards/using.md index 30ab0916d5..6c1cf672af 100644 --- a/explore-analyze/dashboards/using.md +++ b/explore-analyze/dashboards/using.md @@ -16,7 +16,7 @@ mapped_pages: * **Filter pills**, that you can add and combine by clicking on specific parts of the dashboard visualizations, or by defining conditions manually from the filter editor. The filter editor is a good alternative if you’re not comfortable with using KQL expressions in the main query bar. * View the data of a panel and the requests used to build it. -This section shows the most common ways for you to filter dashboard data. For more information about {{kib}} and {{es}} filtering capabilities, refer to [{{kib}} concepts](../overview/kibana-quickstart.md). +This section shows the most common ways for you to filter dashboard data. For more information about {{kib}} and {{es}} filtering capabilities, refer to [](/explore-analyze/query-filter.md). ### Use filter pills [_use_filter_pills] diff --git a/explore-analyze/discover/discover-get-started.md b/explore-analyze/discover/discover-get-started.md index 0027e11f05..a2e561d40b 100644 --- a/explore-analyze/discover/discover-get-started.md +++ b/explore-analyze/discover/discover-get-started.md @@ -14,15 +14,15 @@ Learn how to use **Discover** to: **Prerequisites:** * If you don’t already have {{kib}}, [start a free trial](https://www.elastic.co/cloud/elasticsearch-service/signup?baymax=docs-body&elektra=docs) on Elastic Cloud. -* You must have data in {{es}}. Examples on this page use the [ecommerce sample data set](../overview/kibana-quickstart.md#gs-get-data-into-kibana), but you can use your own data. -* You should have an understanding of [{{es}} documents and indices](../../manage-data/data-store/index-basics.md) and [{{kib}} concepts](../overview/kibana-quickstart.md). +* You must have data in {{es}}. Examples on this page use the [ecommerce sample data set](../index.md#gs-get-data-into-kibana), but you can use your own data. +* You should have an understanding of [{{es}} documents and indices](../../manage-data/data-store/index-basics.md). ## Load data into Discover [find-the-data-you-want-to-use] Select the data you want to explore, and then specify the time range in which to view that data. -1. Find **Discover** in the navigation menu or by using the [global search field](../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Discover** in the navigation menu or by using the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Select the data view that contains the data you want to explore. ::::{tip} By default, {{kib}} requires a [{{data-source}}](../find-and-organize/data-views.md) to access your Elasticsearch data. A {{data-source}} can point to one or more indices, [data streams](../../manage-data/data-store/index-types/data-streams.md), or [index aliases](https://www.elastic.co/guide/en/elasticsearch/reference/current/alias.html). When adding data to {{es}} using one of the many integrations available, sometimes data views are created automatically, but you can also create your own. diff --git a/explore-analyze/discover/discover-search-for-relevance.md b/explore-analyze/discover/discover-search-for-relevance.md index ec51da7b49..a29d10313a 100644 --- a/explore-analyze/discover/discover-search-for-relevance.md +++ b/explore-analyze/discover/discover-search-for-relevance.md @@ -7,7 +7,7 @@ mapped_pages: {{es}} assigns a relevancy, or score to each document, so you can can narrow your search to the documents with the most relevant results. The higher the score, the better it matches your query. -This example shows how to use **Discover** to list your documents from most relevant to least relevant. This example uses the [sample flights data set](../overview/kibana-quickstart.md#gs-get-data-into-kibana), or you can use your own data. +This example shows how to use **Discover** to list your documents from most relevant to least relevant. This example uses the [sample flights data set](../index.md#gs-get-data-into-kibana), or you can use your own data. 1. In **Discover**, open the {{data-source}} dropdown, and select the data that you want to work with. diff --git a/explore-analyze/discover/run-pattern-analysis-discover.md b/explore-analyze/discover/run-pattern-analysis-discover.md index ee5e0d1985..ae69100f32 100644 --- a/explore-analyze/discover/run-pattern-analysis-discover.md +++ b/explore-analyze/discover/run-pattern-analysis-discover.md @@ -9,7 +9,7 @@ Log pattern analysis helps you to find patterns in unstructured log messages and Log pattern analysis works on every text field. -This example uses the [sample web logs data](../overview/kibana-quickstart.md#gs-get-data-into-kibana), or you can use your own data. +This example uses the [sample web logs data](../index.md#gs-get-data-into-kibana), or you can use your own data. 1. Go to **Discover**. 2. Expand the {{data-source}} dropdown, and select **Kibana Sample Data Logs**. diff --git a/explore-analyze/discover/search-sessions.md b/explore-analyze/discover/search-sessions.md index ca24ecfe7a..098109e776 100644 --- a/explore-analyze/discover/search-sessions.md +++ b/explore-analyze/discover/search-sessions.md @@ -39,7 +39,7 @@ You’re trying to understand a trend you see on a dashboard. You need to look a ![Search Session indicator displaying the current state of the search](../../images/kibana-search-session-awhile.png "title =50%") Once you save a search session, you can start a new search, navigate to a different application, or close the browser. -3. To view your saved search sessions, go to the **Search Sessions** management page using the navigation menu or the [global search field](../../get-started/the-stack.md#kibana-navigation-search). For a saved or completed session, you can also open this view from the search sessions popup. +3. To view your saved search sessions, go to the **Search Sessions** management page using the navigation menu or the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md). For a saved or completed session, you can also open this view from the search sessions popup. ![Search Sessions management view with actions for inspecting](../../images/kibana-search-sessions-menu.png "") 4. Use the edit menu in **Search Sessions** to: diff --git a/explore-analyze/discover/show-field-statistics.md b/explore-analyze/discover/show-field-statistics.md index 1be92ebdf5..10b549732d 100644 --- a/explore-analyze/discover/show-field-statistics.md +++ b/explore-analyze/discover/show-field-statistics.md @@ -10,7 +10,7 @@ Explore the fields in your data with the **Field statistics** view in **Discover * What does the latency look like when one of the containers is down on a Sunday? * Is the field type and format in the data view appropriate for the data and its cardinality? -This example explores the fields in the [sample web logs data](../overview/kibana-quickstart.md#gs-get-data-into-kibana), or you can use your own data. +This example explores the fields in the [sample web logs data](../index.md#gs-get-data-into-kibana), or you can use your own data. 1. Go to **Discover**. 2. Expand the {{data-source}} dropdown, and select **Kibana Sample Data Logs**. diff --git a/explore-analyze/discover/try-esql.md b/explore-analyze/discover/try-esql.md index 1ef61c3c90..de21ce3d46 100644 --- a/explore-analyze/discover/try-esql.md +++ b/explore-analyze/discover/try-esql.md @@ -25,7 +25,7 @@ To view the {{esql}} option in **Discover**, the `enableESQL` setting must be en To load the sample data: -1. [Install the web logs sample data](../overview/kibana-quickstart.md#gs-get-data-into-kibana). +1. [Install the web logs sample data](../index.md#gs-get-data-into-kibana). 2. Go to **Discover**. 3. Select **Try {{esql}}** from the application menu bar. diff --git a/explore-analyze/find-and-organize/data-views.md b/explore-analyze/find-and-organize/data-views.md index 548ac0ac4b..51c17e2d64 100644 --- a/explore-analyze/find-and-organize/data-views.md +++ b/explore-analyze/find-and-organize/data-views.md @@ -175,7 +175,7 @@ Deleting a {{data-source}} breaks all visualizations, saved Discover sessions, a :::: -1. Go to the **Data Views** management page using the navigation menu or the [global search field](../../get-started/the-stack.md#kibana-navigation-search). +1. Go to the **Data Views** management page using the navigation menu or the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Find the {{data-source}} that you want to delete, and then click ![Delete icon](../../images/kibana-delete.png "") in the **Actions** column. @@ -213,7 +213,7 @@ For detailed information on how to use runtime fields with {{es}}, refer to [Run To add runtime fields to your data views, open the data view you want to change, then define the field values by emitting a single value using the [Painless scripting language](../../explore-analyze/scripting/modules-scripting-painless.md). You can also add runtime fields in [**Discover**](../../explore-analyze/discover/discover-get-started.md#add-field-in-discover) and [**Lens**](../../explore-analyze/visualize/lens.md#change-the-fields). -1. Go to the **Data Views** management page using the navigation menu or the [global search field](../../get-started/the-stack.md#kibana-navigation-search). +1. Go to the **Data Views** management page using the navigation menu or the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Select the data view that you want to add the runtime field to, then click **Add field**. 3. Enter the field **Name**, then select the **Type**. 4. Select **Set custom label**, then enter the label you want to display where the data view is used, such as **Discover**. @@ -229,7 +229,7 @@ To add runtime fields to your data views, open the data view you want to change, #### Runtime field examples [runtime-field-examples] -Try the runtime field examples on your own using the [**Sample web logs**](../../explore-analyze/overview/kibana-quickstart.md#gs-get-data-into-kibana) data. +Try the runtime field examples on your own using the [**Sample web logs**](../../explore-analyze/index.md#gs-get-data-into-kibana) data. #### Return a keyword value [simple-hello-world-example] @@ -315,7 +315,7 @@ else { Edit the settings for runtime fields, or remove runtime fields from data views. -1. Go to the **Data Views** management page using the navigation menu or the [global search field](../../get-started/the-stack.md#kibana-navigation-search). +1. Go to the **Data Views** management page using the navigation menu or the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Select the data view that contains the runtime field you want to manage, then open the runtime field edit options or delete the runtime field. @@ -450,7 +450,7 @@ The ability to create new scripted fields has been removed from the **Data Views :::: -1. Go to the **Data Views** management page using the navigation menu or the [global search field](../../get-started/the-stack.md#kibana-navigation-search). +1. Go to the **Data Views** management page using the navigation menu or the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Select the data view that contains the scripted field you want to manage. 3. Select the **Scripted fields** tab, then open the scripted field edit options or delete the scripted field. @@ -466,7 +466,7 @@ Built-in validation is unsupported for scripted fields. When your scripts contai {{kib}} uses the same field types as {{es}}, however, some {{es}} field types are unsupported in {{kib}}. To customize how {{kib}} displays data fields, use the formatting options. -1. Go to the **Data Views** management page using the navigation menu or the [global search field](../../get-started/the-stack.md#kibana-navigation-search). +1. Go to the **Data Views** management page using the navigation menu or the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click the data view that contains the field you want to change. 3. Find the field, then open the edit options (![Data field edit icon](../../images/kibana-edit_icon.png "")). 4. Select **Set custom label**, then enter a **Custom label** for the field. diff --git a/explore-analyze/find-and-organize/saved-objects.md b/explore-analyze/find-and-organize/saved-objects.md index d79c3a319c..2e0fc75600 100644 --- a/explore-analyze/find-and-organize/saved-objects.md +++ b/explore-analyze/find-and-organize/saved-objects.md @@ -24,9 +24,20 @@ $$$managing-saved-objects-export-objects$$$ $$$managing-saved-objects-share-to-space$$$ +{{kib}} lets you save objects for your own future use or for sharing with others. Each saved object type has different abilities. For example, you can save your search queries made with **Discover**, which lets you: + +* Share a link to your search +* Download the full search results in CSV form +* Start an aggregated visualization using the same search query +* Embed the **Discover** search results into a dashboard + +For organization, every saved object can have a name, [tags](tags.md), and type. Use the global search to quickly open a saved object. + +## Manage saved objects + Edit, import, export, and copy your saved objects. These objects include dashboards, visualizations, maps, {{data-sources}}, **Canvas** workpads, and other saved objects. -You can find the **Saved Objects** page using the navigation menu or the [global search field](/get-started/the-stack.md#kibana-navigation-search). +You can find the **Saved Objects** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). :::{image} ../../images/kibana-management-saved-objects.png :alt: Saved Objects diff --git a/explore-analyze/find-and-organize/tags.md b/explore-analyze/find-and-organize/tags.md index a0a55dd289..c0562b2568 100644 --- a/explore-analyze/find-and-organize/tags.md +++ b/explore-analyze/find-and-organize/tags.md @@ -16,7 +16,7 @@ mapped_urls: Use tags to categorize your saved objects, then filter for related objects based on shared tags. -To get started, go to the **Tags** management page using the navigation menu or the [global search field](../../get-started/the-stack.md#kibana-navigation-search). +To get started, go to the **Tags** management page using the navigation menu or the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md). :::{image} ../../images/kibana-tag-management-section.png :alt: Tags management diff --git a/explore-analyze/index.md b/explore-analyze/index.md index 0a2495eb92..4d4e30cbbd 100644 --- a/explore-analyze/index.md +++ b/explore-analyze/index.md @@ -2,6 +2,7 @@ mapped_urls: - https://www.elastic.co/guide/en/serverless/current/elasticsearch-explore-your-data.html - https://www.elastic.co/guide/en/kibana/current/introduction.html#visualize-and-analyze + - https://www.elastic.co/guide/en/kibana/current/get-started.html --- # Explore and analyze @@ -19,6 +20,63 @@ $$$elasticsearch-explore-your-data-visualizations-save-to-the-visualize-library$ The Elasticsearch platform and its UI, also known as Kibana, provide a comprehensive suite of tools to help you search, interact with, explore, and analyze your data effectively. These features empower you to gain deep insights, uncover trends, and take actionable steps based on your findings. This page is an overview of the key capabilities. +:::{dropdown} Accessibility statement + +Elastic is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience, and strive toward ensuring our tools are usable by everyone. + + +**Measures to support accessibility** +Elastic takes the following measures to ensure accessibility of Kibana: + +* Maintains and incorporates an [accessible component library](https://elastic.github.io/eui/). +* Provides continual accessibility training for our staff. +* Employs a third-party audit. + + +**Conformance status** +Kibana aims to meet [WCAG 2.1 level AA](https://www.w3.org/WAI/WCAG21/quickref/?currentsidebar=%23col_customize&levels=aaa&technologies=server%2Csmil%2Cflash%2Csl) compliance. Currently, we can only claim to partially conform, meaning we do not fully meet all of the success criteria. However, we do try to take a broader view of accessibility, and go above and beyond the legal and regulatory standards to provide a good experience for all of our users. + + +**Feedback** +We welcome your feedback on the accessibility of Kibana. Please let us know if you encounter accessibility barriers on Kibana by either emailing us at `accessibility@elastic.co` or opening [an issue on GitHub](https://github.com/elastic/kibana/issues/new?labels=Project%3AAccessibility&template=Accessibility.md&title=%28Accessibility%29). + + +**Technical specifications** +Accessibility of Kibana relies on the following technologies to work with your web browser and any assistive technologies or plugins installed on your computer: + +* HTML +* CSS +* JavaScript +* WAI-ARIA + + +**Limitations and alternatives** +Despite our best efforts to ensure accessibility of Kibana, there are some limitations. Please [open an issue on GitHub](https://github.com/elastic/kibana/issues/new?labels=Project%3AAccessibility&template=Accessibility.md&title=%28Accessibility%29) if you observe an issue not in this list. + +Known limitations are in the following areas: + +* **Charts**: We have a clear plan for the first steps of making charts accessible. We’ve opened this [Charts accessibility ticket on GitHub](https://github.com/elastic/elastic-charts/issues/300) for tracking our progress. +* **Maps**: Maps might pose difficulties to users with vision disabilities. We welcome your input on making our maps accessible. Go to the [Maps accessibility ticket on GitHub](https://github.com/elastic/kibana/issues/57271) to join the discussion and view our plans. +* **Tables**: Although generally accessible and marked-up as standard HTML tables with column headers, tables rarely make use of row headers and have poor captions. You will see incremental improvements as various applications adopt a new accessible component. +* **Color contrast**: Modern Kibana interfaces generally do not have color contrast issues. However, older code might fall below the recommended contrast levels. As we continue to update our code, this issue will phase out naturally. + +To see individual tickets, view our [GitHub issues with label "`Project:Accessibility`"](https://github.com/elastic/kibana/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3AProject%3AAccessibility). + + +**Assessment approach** +Elastic assesses the accessibility of Kibana with the following approaches: + +* **Self-evaluation**: Our employees are familiar with accessibility standards and review new designs and implemented features to confirm that they are accessible. +* **External evaluation**: We engage external contractors to help us conduct an independent assessment and generate a formal VPAT. Please email `accessibility@elastic.co` if you’d like a copy. +* **Automated evaluation**: We are starting to run [axe](https://www.deque.com/axe/) on every page. See our current progress in the [automated testing GitHub issue](https://github.com/elastic/kibana/issues/51456). + +Manual testing largely focuses on screen reader support and is done on: + +* VoiceOver on MacOS with Safari, Chrome and Edge +* NVDA on Windows with Chrome and Firefox + +::: + ## Querying and filtering Elasticsearch’s robust query capabilities enable you to retrieve specific data from your datasets. Using the Query DSL (Domain Specific Language), you can build powerful, flexible queries that support: @@ -48,24 +106,29 @@ Elasticsearch integrates machine learning for proactive analytics, helping you t - Perform powerful NLP operations such as semantic search - Machine learning models simplify complex predictive tasks, unlocking new opportunities for optimization. -## Discover -Discover lets you interact directly with raw data. Use Discover to: +## Explore with Discover [explore-the-data] + +[Discover](/explore-analyze/discover.md) lets you interact directly with raw data. Use Discover to: - Browse documents in your indices - Apply filters and search queries - Visualize results in real-time It’s the starting point for exploratory analysis. -## Dashboards -Dashboards serve as centralized hubs for visualizing and monitoring data insights. With Dashboards, you can: +## Visualize the data [view-and-analyze-the-data] + +Create a variety of visualizations and add them to a dashboard. + +### Dashboards +[Dashboards](/explore-analyze/dashboards.md) serve as centralized hubs for visualizing and monitoring data insights. With Dashboards, you can: - Combine multiple visualizations into a single, unified view - Display data from multiple indices or datasets for comprehensive analysis - Customize layouts to suit specific workflows and preferences -Dashboards provide an interactive and cohesive environment to explore trends and metrics at a glance. +Dashboards provide an interactive and cohesive environment with filtering capabilities and controls to explore trends and metrics at a glance. -## Panels and visualizations -Panels and visualizations are the core elements that populate your dashboards, enabling dynamic data representation. They support diverse chart types, Interactive filtering, and drill-down capabilities to explore data further. These building blocks transform raw data into clear, actionable visuals, allowing users to analyze and interpret results effectively. +### Panels and visualizations +[Panels and visualizations](/explore-analyze/visualize.md) are the core elements that populate your dashboards, enabling dynamic data representation. They support diverse chart types, Interactive filtering, and drill-down capabilities to explore data further. These building blocks transform raw data into clear, actionable visuals, allowing users to analyze and interpret results effectively. ## Reporting and sharing You can share your work and findings with colleagues and stakeholders or generate reports. Report generation can be scheduled or on-demand. You can choose from multiple formats (for example, PDF, CSV). These tools ensure that actionable insights reach the right people at the right time. @@ -75,3 +138,19 @@ You can set up alerts to monitor your data continuously. Alerts notify you when ## Bringing it all together Elasticsearch's features integrate seamlessly, offering an end-to-end solution for exploring, analyzing, and acting on data. If you want to explore any of the listed features in greater depth, refer to their respective documentation pages and check the provided hands-on examples and tutorials. +If you'd like to explore some features but don't have data ready yet, some sample data sets are available in {{kib}} for you to install and play with. + +### Add sample data [gs-get-data-into-kibana] + +Sample data sets come with sample visualizations, dashboards, and more to help you explore {{kib}} before you ingest or add your own data. + +1. Open the **Integrations** page from the navigation menu or using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). +2. In the list of integrations, select **Sample Data**. +3. On the page that opens, select **Other sample data sets**. +4. Install the sample data sets that you want. + +Once installed, you can access the sample data in the various {{kib}} apps available to you. + + + + diff --git a/explore-analyze/machine-learning/anomaly-detection/geographic-anomalies.md b/explore-analyze/machine-learning/anomaly-detection/geographic-anomalies.md index aaf0dfc132..c6cc55842c 100644 --- a/explore-analyze/machine-learning/anomaly-detection/geographic-anomalies.md +++ b/explore-analyze/machine-learning/anomaly-detection/geographic-anomalies.md @@ -18,7 +18,7 @@ To run this type of {{anomaly-job}}, you must have [{{ml-features}} set up](../s The latitude and longitude must be in the range -180 to 180 and represent a point on the surface of the Earth. -This example uses the sample eCommerce orders and sample web logs data sets. For more information, see [Add the sample data](../../overview/kibana-quickstart.md#gs-get-data-into-kibana). +This example uses the sample eCommerce orders and sample web logs data sets. For more information, see [Add the sample data](../../index.md#gs-get-data-into-kibana). ## Explore your geographic data [geographic-anomalies-visualize] diff --git a/explore-analyze/machine-learning/anomaly-detection/mapping-anomalies.md b/explore-analyze/machine-learning/anomaly-detection/mapping-anomalies.md index 40623a57e2..ad20afdd2e 100644 --- a/explore-analyze/machine-learning/anomaly-detection/mapping-anomalies.md +++ b/explore-analyze/machine-learning/anomaly-detection/mapping-anomalies.md @@ -11,7 +11,7 @@ If your data includes vector layers that are defined in the [{{ems}} ({{ems-init If you want to view choropleth maps in **{{data-viz}}** or {{anomaly-job}} results, you must have fields that contain valid vector layers (such as [country codes](https://maps.elastic.co/#file/world_countries) or [postal codes](https://maps.elastic.co/#file/usa_zip_codes)). -This example uses the sample web logs data set. For more information, see [Add the sample data](../../overview/kibana-quickstart.md#gs-get-data-into-kibana). +This example uses the sample web logs data set. For more information, see [Add the sample data](../../index.md#gs-get-data-into-kibana). ## Explore your data [visualize-vector-layers] diff --git a/explore-analyze/machine-learning/anomaly-detection/ml-ad-run-jobs.md b/explore-analyze/machine-learning/anomaly-detection/ml-ad-run-jobs.md index b7dabe3b36..66f54c5dcd 100644 --- a/explore-analyze/machine-learning/anomaly-detection/ml-ad-run-jobs.md +++ b/explore-analyze/machine-learning/anomaly-detection/ml-ad-run-jobs.md @@ -19,7 +19,7 @@ If your data is located outside of {{es}}, you cannot use {{kib}} to create your ## Create an {{anomaly-job}} [ml-ad-create-job] -You can create {{anomaly-jobs}} by using the [create {{anomaly-jobs}} API](https://www.elastic.co/guide/en/elasticsearch/reference/current/ml-put-job.html). {{kib}} also provides wizards to simplify the process, which vary depending on whether you are using the {{ml-app}} app, {{security-app}} or {{observability}} apps. To open **Anomaly Detection**, find **{{ml-app}}** in the main menu, or use the [global search field](../../overview/kibana-quickstart.md#_finding_your_apps_and_objects). +You can create {{anomaly-jobs}} by using the [create {{anomaly-jobs}} API](https://www.elastic.co/guide/en/elasticsearch/reference/current/ml-put-job.html). {{kib}} also provides wizards to simplify the process, which vary depending on whether you are using the {{ml-app}} app, {{security-app}} or {{observability}} apps. To open **Anomaly Detection**, find **{{ml-app}}** in the main menu, or use the [global search field](../../find-and-organize/find-apps-and-objects.md). :::{image} ../../../images/machine-learning-ml-create-job.png :alt: Create New Job diff --git a/explore-analyze/machine-learning/anomaly-detection/ml-configuring-categories.md b/explore-analyze/machine-learning/anomaly-detection/ml-configuring-categories.md index ac62f839bc..70bf86706e 100644 --- a/explore-analyze/machine-learning/anomaly-detection/ml-configuring-categories.md +++ b/explore-analyze/machine-learning/anomaly-detection/ml-configuring-categories.md @@ -20,7 +20,7 @@ Categorization is a {{ml}} process that tokenizes a text field, clusters similar ## Creating categorization jobs [creating-categorization-jobs] -1. In {{kib}}, navigate to **Jobs**. To open **Jobs**, find **{{ml-app}} > Anomaly Detection** in the main menu, or use the [global search field](../../overview/kibana-quickstart.md#_finding_your_apps_and_objects). +1. In {{kib}}, navigate to **Jobs**. To open **Jobs**, find **{{ml-app}} > Anomaly Detection** in the main menu, or use the [global search field](../../find-and-organize/find-apps-and-objects.md). 2. Click **Create job**, select the data view you want to analyze. 3. Select the **Categorization** wizard from the list. 4. Choose a categorization detector - it’s the `count` function in this example - and the field you want to categorize - the `message` field in this example. diff --git a/explore-analyze/machine-learning/anomaly-detection/ml-getting-started.md b/explore-analyze/machine-learning/anomaly-detection/ml-getting-started.md index 1785cb20d6..b30c705b42 100644 --- a/explore-analyze/machine-learning/anomaly-detection/ml-getting-started.md +++ b/explore-analyze/machine-learning/anomaly-detection/ml-getting-started.md @@ -26,7 +26,7 @@ Need more context? Check out the [{{es}} introduction](https://www.elastic.co/gu :::: 2. Verify that your environment is set up properly to use the {{ml-features}}. If the {{es}} {{security-features}} are enabled, to complete this tutorial you need a user that has authority to manage {{anomaly-jobs}}. See [Setup and security](../setting-up-machine-learning.md). -3. [Add the sample data sets that ship with {{kib}}](../../overview/kibana-quickstart.md#gs-get-data-into-kibana). +3. [Add the sample data sets that ship with {{kib}}](../../index.md#gs-get-data-into-kibana). 1. From the {{kib}} home page, click **Try sample data**, then open the **Other sample data sets** section. 2. Pick a data set. In this tutorial, you’ll use the **Sample web logs**. While you’re here, feel free to click **Add data** on all of the available sample data sets. @@ -43,7 +43,7 @@ To get the best results from {{ml}} analytics, you must understand your data. Yo The {{kib}} {{ml-features}} use pop-ups. You must configure your web browser so that it does not block pop-up windows or create an exception for your {{kib}} URL. :::: -2. Open **Machine Learning** from the main menu, or use the [global search field](../../overview/kibana-quickstart.md#_finding_your_apps_and_objects). +2. Open **Machine Learning** from the main menu, or use the [global search field](../../find-and-organize/find-apps-and-objects.md). 3. Select the **{{data-viz}}** tab. 4. Click **Select data view** and choose the `kibana_sample_data_logs` {{data-source}}. 5. Use the time filter to select a time period that you’re interested in exploring. Alternatively, click **Use full data** to view the full time range of data. diff --git a/explore-analyze/machine-learning/anomaly-detection/ml-jobs-from-lens.md b/explore-analyze/machine-learning/anomaly-detection/ml-jobs-from-lens.md index bcce0ae5a1..f890b3f5b9 100644 --- a/explore-analyze/machine-learning/anomaly-detection/ml-jobs-from-lens.md +++ b/explore-analyze/machine-learning/anomaly-detection/ml-jobs-from-lens.md @@ -22,7 +22,7 @@ You can create {{anomaly-jobs}} from the compatible Lens charts on **Dashboard** You need to have a compatible visualization on **Dashboard** to create an {{anomaly-job}}. If you don’t have one but you want to try the feature out, go to **Analytics > Dashboard** and select the `[Flight] Global Flight Dashboard` which is based on the {{kib}} sample flight data set. Select the `Flight count` visualization from the dashboard. :::: -1. Go to **Analytics > Dashboard** from the main menu, or use the [global search field](../../overview/kibana-quickstart.md#_finding_your_apps_and_objects). Select a dashboard with a compatible visualization. +1. Go to **Analytics > Dashboard** from the main menu, or use the [global search field](../../find-and-organize/find-apps-and-objects.md). Select a dashboard with a compatible visualization. 2. Open the **Options (…​) menu** for the panel, then select **More**. 3. Select **Create {{anomaly-job}}**. The option is only displayed if the visualization can be converted to an {{anomaly-job}} configuration. 4. (Optional) Select the layer from which the {{anomaly-job}} is created. diff --git a/explore-analyze/machine-learning/anomaly-detection/ml-reverting-model-snapshot.md b/explore-analyze/machine-learning/anomaly-detection/ml-reverting-model-snapshot.md index 4afe700742..93ecab968f 100644 --- a/explore-analyze/machine-learning/anomaly-detection/ml-reverting-model-snapshot.md +++ b/explore-analyze/machine-learning/anomaly-detection/ml-reverting-model-snapshot.md @@ -7,7 +7,7 @@ mapped_pages: [Snapshots of the {{ml}} model](ml-ad-run-jobs.md#ml-ad-model-snapshots) for each {{anomaly-job}} are saved frequently to an internal {{es}} index to ensure resilience. It makes it possible to reset the model to a previous state in case of a system failure or if the model changed significantly due to a one-off event. -1. In {{kib}}, navigate to **Jobs**. To open **Jobs**, find **{{ml-app}} > Anomaly Detection** in the main menu, or use the [global search field](../../overview/kibana-quickstart.md#_finding_your_apps_and_objects). +1. In {{kib}}, navigate to **Jobs**. To open **Jobs**, find **{{ml-app}} > Anomaly Detection** in the main menu, or use the [global search field](../../find-and-organize/find-apps-and-objects.md). 2. Locate the {{anomaly-job}} whose model you want to revert in the job table. 3. Open the job details and navigate to the **Model Snapshots** tab. diff --git a/explore-analyze/machine-learning/data-frame-analytics/ml-dfa-classification.md b/explore-analyze/machine-learning/data-frame-analytics/ml-dfa-classification.md index 0862a68a3e..7675eecbff 100644 --- a/explore-analyze/machine-learning/data-frame-analytics/ml-dfa-classification.md +++ b/explore-analyze/machine-learning/data-frame-analytics/ml-dfa-classification.md @@ -155,7 +155,7 @@ To learn more about choosing the class assignment objective that fits your goal, The model that you created is stored as {{es}} documents in internal indices. In other words, the characteristics of your trained model are saved and ready to be deployed and used as functions. -1. To deploy {{dfanalytics}} model in a pipeline, navigate to **Machine Learning** > **Model Management** > **Trained models** in the main menu, or use the [global search field](../../overview/kibana-quickstart.md#_finding_your_apps_and_objects) in {{kib}}. +1. To deploy {{dfanalytics}} model in a pipeline, navigate to **Machine Learning** > **Model Management** > **Trained models** in the main menu, or use the [global search field](../../find-and-organize/find-apps-and-objects.md) in {{kib}}. 2. Find the model you want to deploy in the list and click **Deploy model** in the **Actions** menu. :::{image} ../../../images/machine-learning-ml-dfa-trained-models-ui.png @@ -207,7 +207,7 @@ If you use trained model aliases to reference your trained model in an {{infer}} ## Performing {{classanalysis}} in the sample flight data set [performing-classification] -Let’s try to predict whether a flight will be delayed or not by using the [sample flight data](../../overview/kibana-quickstart.md#gs-get-data-into-kibana). The data set contains information such as weather conditions, carrier, flight distance, origin, destination, and whether or not the flight was delayed. The {{classification}} model learns the relationships between the fields in your data to predict the value of the *dependent variable*, which in this case is the boolean `FlightDelay` field. +Let’s try to predict whether a flight will be delayed or not by using the [sample flight data](../../index.md#gs-get-data-into-kibana). The data set contains information such as weather conditions, carrier, flight distance, origin, destination, and whether or not the flight was delayed. The {{classification}} model learns the relationships between the fields in your data to predict the value of the *dependent variable*, which in this case is the boolean `FlightDelay` field. ::::{tip} If you want to view this example in a Jupyter notebook, [click here](https://github.com/elastic/examples/tree/master/Machine%20Learning/Analytics%20Jupyter%20Notebooks). diff --git a/explore-analyze/machine-learning/data-frame-analytics/ml-dfa-finding-outliers.md b/explore-analyze/machine-learning/data-frame-analytics/ml-dfa-finding-outliers.md index dc3c1fab95..68febeee94 100644 --- a/explore-analyze/machine-learning/data-frame-analytics/ml-dfa-finding-outliers.md +++ b/explore-analyze/machine-learning/data-frame-analytics/ml-dfa-finding-outliers.md @@ -109,7 +109,7 @@ The evaluate {{dfanalytics}} API can return the false positive rate (`fpr`) and ## Detecting unusual behavior in the logs data set [weblogs-outliers] -The goal of {{oldetection}} is to find the most unusual documents in an index. Let’s try to detect unusual behavior in the [data logs sample data set](../../overview/kibana-quickstart.md#gs-get-data-into-kibana). +The goal of {{oldetection}} is to find the most unusual documents in an index. Let’s try to detect unusual behavior in the [data logs sample data set](../../index.md#gs-get-data-into-kibana). 1. Verify that your environment is set up properly to use {{ml-features}}. If the {{es}} {{security-features}} are enabled, you need a user that has authority to create and manage {{dfanalytics}} jobs. See [Setup and security](../setting-up-machine-learning.md). Since we’ll be creating {{transforms}}, you also need `manage_data_frame_transforms` cluster privileges. diff --git a/explore-analyze/machine-learning/data-frame-analytics/ml-dfa-regression.md b/explore-analyze/machine-learning/data-frame-analytics/ml-dfa-regression.md index 39bd29ecc8..535aefc2f7 100644 --- a/explore-analyze/machine-learning/data-frame-analytics/ml-dfa-regression.md +++ b/explore-analyze/machine-learning/data-frame-analytics/ml-dfa-regression.md @@ -101,7 +101,7 @@ R-squared (R^2^) represents the goodness of fit and measures how much of the var The model that you created is stored as {{es}} documents in internal indices. In other words, the characteristics of your trained model are saved and ready to be deployed and used as functions. The [{{infer}}](#ml-inference-reg) feature enables you to use your model in a preprocessor of an ingest pipeline or in a pipeline aggregation of a search query to make predictions about your data. -1. To deploy {{dfanalytics}} model in a pipeline, navigate to **Machine Learning** > **Model Management** > **Trained models** in the main menu, or use the [global search field](../../overview/kibana-quickstart.md#_finding_your_apps_and_objects) in {{kib}}. +1. To deploy {{dfanalytics}} model in a pipeline, navigate to **Machine Learning** > **Model Management** > **Trained models** in the main menu, or use the [global search field](../../find-and-organize/find-apps-and-objects.md) in {{kib}}. 2. Find the model you want to deploy in the list and click **Deploy model** in the **Actions** menu. :::{image} ../../../images/machine-learning-ml-dfa-trained-models-ui.png @@ -153,7 +153,7 @@ If you use trained model aliases to reference your trained model in an {{infer}} ## Performing {{reganalysis}} in the sample flight data set [performing-regression] -Let’s try to predict flight delays by using the [sample flight data](../../overview/kibana-quickstart.md#gs-get-data-into-kibana). The data set contains information such as weather conditions, flight destinations and origins, flight distances, carriers, and the number of minutes each flight was delayed. When you create a {{regression}} job, it learns the relationships between the fields in your data to predict the value of a *{{depvar}}*, which - in this case - is the numeric `FlightDelayMins` field. For an overview of these concepts, see [*Predicting numerical values with {{regression}}*]() and [Introduction to supervised learning](ml-dfa-overview.md#ml-supervised-workflow). +Let’s try to predict flight delays by using the [sample flight data](../../index.md#gs-get-data-into-kibana). The data set contains information such as weather conditions, flight destinations and origins, flight distances, carriers, and the number of minutes each flight was delayed. When you create a {{regression}} job, it learns the relationships between the fields in your data to predict the value of a *{{depvar}}*, which - in this case - is the numeric `FlightDelayMins` field. For an overview of these concepts, see [*Predicting numerical values with {{regression}}*]() and [Introduction to supervised learning](ml-dfa-overview.md#ml-supervised-workflow). ### Preparing your data [flightdata-regression-data] diff --git a/explore-analyze/machine-learning/data-frame-analytics/ml-trained-models.md b/explore-analyze/machine-learning/data-frame-analytics/ml-trained-models.md index 69639ecfc4..e29f6a20a9 100644 --- a/explore-analyze/machine-learning/data-frame-analytics/ml-trained-models.md +++ b/explore-analyze/machine-learning/data-frame-analytics/ml-trained-models.md @@ -15,7 +15,7 @@ Alternatively, you can use APIs like [get trained models](https://www.elastic.co ### Models trained by {{dfanalytics}} [_models_trained_by_dfanalytics] -1. To deploy {{dfanalytics}} model in a pipeline, navigate to **Machine Learning** > **Model Management** > **Trained models** in the main menu, or use the [global search field](../../overview/kibana-quickstart.md#_finding_your_apps_and_objects) in {{kib}}. +1. To deploy {{dfanalytics}} model in a pipeline, navigate to **Machine Learning** > **Model Management** > **Trained models** in the main menu, or use the [global search field](../../find-and-organize/find-apps-and-objects.md) in {{kib}}. 2. Find the model you want to deploy in the list and click **Deploy model** in the **Actions** menu. diff --git a/explore-analyze/machine-learning/machine-learning-in-kibana.md b/explore-analyze/machine-learning/machine-learning-in-kibana.md index c655ab5db8..e25d9b3fec 100644 --- a/explore-analyze/machine-learning/machine-learning-in-kibana.md +++ b/explore-analyze/machine-learning/machine-learning-in-kibana.md @@ -46,7 +46,7 @@ There are limitations in {{ml-features}} that affect {{kib}}. For more informati This functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. :::: -You can find the data drift view in **{{ml-app}}** > **{{data-viz}}** in {{kib}} or by using the [global search field](../../get-started/the-stack.md#kibana-navigation-search). The data drift view shows you the differences in each field for two different time ranges in a given {{data-source}}. The view helps you to visualize the changes in your data over time and enables you to understand its behavior better. +You can find the data drift view in **{{ml-app}}** > **{{data-viz}}** in {{kib}} or by using the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md). The data drift view shows you the differences in each field for two different time ranges in a given {{data-source}}. The view helps you to visualize the changes in your data over time and enables you to understand its behavior better. :::{image} ../../images/kibana-ml-data-drift.png :alt: Data drift view in {kib} diff --git a/explore-analyze/machine-learning/machine-learning-in-kibana/xpack-ml-aiops.md b/explore-analyze/machine-learning/machine-learning-in-kibana/xpack-ml-aiops.md index b81a7eee4d..4cca57423c 100644 --- a/explore-analyze/machine-learning/machine-learning-in-kibana/xpack-ml-aiops.md +++ b/explore-analyze/machine-learning/machine-learning-in-kibana/xpack-ml-aiops.md @@ -14,7 +14,7 @@ AIOps Labs is a part of {{ml-app}} in {{kib}} which provides features that use a Log rate analysis uses advanced statistical methods to identify reasons for increases or decreases in log rates and displays the statistically significant data in a tabular format. It makes it easy to find and investigate causes of unusual spikes or drops by using the analysis workflow view. Examine the histogram chart of the log rates for a given {{data-source}}, and find the reason behind a particular change possibly in millions of log events across multiple fields and values. -You can find log rate analysis embedded in multiple applications. In {{kib}}, you can find it under **{{ml-app}}** > **AIOps Labs** or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Here, you can select the {{data-source}} or saved Discover session that you want to analyze. +You can find log rate analysis embedded in multiple applications. In {{kib}}, you can find it under **{{ml-app}}** > **AIOps Labs** or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Here, you can select the {{data-source}} or saved Discover session that you want to analyze. :::{image} ../../../images/kibana-ml-log-rate-analysis-before.png :alt: Log event histogram chart @@ -34,7 +34,7 @@ Brushes in the chart show the baseline time range and the deviation in the analy Log pattern analysis helps you to find patterns in unstructured log messages and makes it easier to examine your data. It performs categorization analysis on a selected field of a {{data-source}}, creates categories based on the data and displays them together with a chart that shows the distribution of each category and an example document that matches the category. -You can find log pattern analysis under **{{ml-app}}** > **AIOps Labs** or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Here, you can select the {{data-source}} or saved Discover session that you want to analyze, or in **Discover** as an available action for any text field. +You can find log pattern analysis under **{{ml-app}}** > **AIOps Labs** or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Here, you can select the {{data-source}} or saved Discover session that you want to analyze, or in **Discover** as an available action for any text field. :::{image} ../../../images/kibana-ml-log-pattern-analysis.png :alt: Log pattern analysis UI @@ -51,7 +51,7 @@ This functionality is in technical preview and may be changed or removed in a fu Change point detection uses the [change point aggregation](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-change-point-aggregation.html) to detect distribution changes, trend changes, and other statistically significant change points in a metric of your time series data. -You can find change point detection under **{{ml-app}}** > **AIOps Labs** or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Here, you can select the {{data-source}} or saved Discover session that you want to analyze. +You can find change point detection under **{{ml-app}}** > **AIOps Labs** or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Here, you can select the {{data-source}} or saved Discover session that you want to analyze. :::{image} ../../../images/kibana-ml-change-point-detection.png :alt: Change point detection UI diff --git a/explore-analyze/machine-learning/nlp/ml-nlp-e5.md b/explore-analyze/machine-learning/nlp/ml-nlp-e5.md index 47b6d1f3e2..949f21006c 100644 --- a/explore-analyze/machine-learning/nlp/ml-nlp-e5.md +++ b/explore-analyze/machine-learning/nlp/ml-nlp-e5.md @@ -57,7 +57,7 @@ For most cases, the preferred version is the **Intel and Linux optimized** model #### Using the Trained Models page [trained-model-e5] -1. In {{kib}}, navigate to **{{ml-app}}** > **Trained Models** from the main menu, or use the [global search field](../../overview/kibana-quickstart.md#_finding_your_apps_and_objects). E5 can be found in the list of trained models. There are two versions available: one portable version which runs on any hardware and one version which is optimized for Intel® silicon. You can see which model is recommended to use based on your hardware configuration. +1. In {{kib}}, navigate to **{{ml-app}}** > **Trained Models** from the main menu, or use the [global search field](../../find-and-organize/find-apps-and-objects.md). E5 can be found in the list of trained models. There are two versions available: one portable version which runs on any hardware and one version which is optimized for Intel® silicon. You can see which model is recommended to use based on your hardware configuration. 2. Click the **Add trained model** button. Select the E5 model version you want to use in the opening modal window. The model that is recommended for you based on your hardware configuration is highlighted. Click **Download**. You can check the download status on the **Notifications** page. :::{image} ../../../images/machine-learning-ml-nlp-e5-download.png @@ -171,7 +171,7 @@ For a file-based access, follow these steps: 4. Repeat step 2 and step 3 on all master-eligible nodes. 5. [Restart](../../../deploy-manage/maintenance/start-stop-services/full-cluster-restart-rolling-restart-procedures.md#restart-cluster-rolling) the master-eligible nodes one by one. -6. Navigate to the **Trained Models** page from the main menu, or use the [global search field](../../overview/kibana-quickstart.md#_finding_your_apps_and_objects) in {{kib}}. E5 can be found in the list of trained models. +6. Navigate to the **Trained Models** page from the main menu, or use the [global search field](../../find-and-organize/find-apps-and-objects.md) in {{kib}}. E5 can be found in the list of trained models. 7. Click the **Add trained model** button, select the E5 model version you downloaded in step 1 and want to deploy and click **Download**. The selected model will be downloaded from the model directory where you put in step 2. 8. After the download is finished, start the deployment by clicking the **Start deployment** button. 9. Provide a deployment ID, select the priority, and set the number of allocations and threads per allocation values. diff --git a/explore-analyze/machine-learning/nlp/ml-nlp-elser.md b/explore-analyze/machine-learning/nlp/ml-nlp-elser.md index e15532e782..4ccfb641e3 100644 --- a/explore-analyze/machine-learning/nlp/ml-nlp-elser.md +++ b/explore-analyze/machine-learning/nlp/ml-nlp-elser.md @@ -226,7 +226,7 @@ You can use any HTTP service to deploy ELSER. This example uses the official Ngi 6. Repeat step 5 on all master-eligible nodes. 7. [Restart](../../../deploy-manage/maintenance/start-stop-services/full-cluster-restart-rolling-restart-procedures.md#restart-cluster-rolling) the master-eligible nodes one by one. -8. Navigate to the **Trained Models** page from the main menu, or use the [global search field](../../overview/kibana-quickstart.md#_finding_your_apps_and_objects) in {{kib}}. ELSER can be found in the list of trained models. +8. Navigate to the **Trained Models** page from the main menu, or use the [global search field](../../find-and-organize/find-apps-and-objects.md) in {{kib}}. ELSER can be found in the list of trained models. 9. Click the **Add trained model** button, select the ELSER model version you downloaded in step 1 and want to deploy, and click **Download**. The selected model will be downloaded from the HTTP/HTTPS server you configured. 10. After the download is finished, start the deployment by clicking the **Start deployment** button. 11. Provide a deployment ID, select the priority, and set the number of allocations and threads per allocation values. @@ -252,7 +252,7 @@ For a file-based access, follow these steps: 4. Repeat step 2 and step 3 on all master-eligible nodes. 5. [Restart](../../../deploy-manage/maintenance/start-stop-services/full-cluster-restart-rolling-restart-procedures.md#restart-cluster-rolling) the master-eligible nodes one by one. -6. Navigate to the **Trained Models** page from the main menu, or use the [global search field](../../overview/kibana-quickstart.md#_finding_your_apps_and_objects) in {{kib}}. ELSER can be found in the list of trained models. +6. Navigate to the **Trained Models** page from the main menu, or use the [global search field](../../find-and-organize/find-apps-and-objects.md) in {{kib}}. ELSER can be found in the list of trained models. 7. Click the **Add trained model** button, select the ELSER model version you downloaded in step 1 and want to deploy and click **Download**. The selected model will be downloaded from the model directory where you put in step 2. 8. After the download is finished, start the deployment by clicking the **Start deployment** button. 9. Provide a deployment ID, select the priority, and set the number of allocations and threads per allocation values. @@ -260,7 +260,7 @@ For a file-based access, follow these steps: ## Testing ELSER [_testing_elser] -You can test the deployed model in {{kib}}. Navigate to **Model Management** > **Trained Models** from the main menu, or use the [global search field](../../overview/kibana-quickstart.md#_finding_your_apps_and_objects) in {{kib}}. Locate the deployed ELSER model in the list of trained models, then select **Test model** from the Actions menu. +You can test the deployed model in {{kib}}. Navigate to **Model Management** > **Trained Models** from the main menu, or use the [global search field](../../find-and-organize/find-apps-and-objects.md) in {{kib}}. Locate the deployed ELSER model in the list of trained models, then select **Test model** from the Actions menu. You can use data from an existing index to test the model. Select the index, then a field of the index you want to test ELSER on. Provide a search query and click **Test**. Evaluating model recall is simpler when using a query related to the documents. diff --git a/explore-analyze/machine-learning/nlp/ml-nlp-inference.md b/explore-analyze/machine-learning/nlp/ml-nlp-inference.md index b407bcac65..a049195908 100644 --- a/explore-analyze/machine-learning/nlp/ml-nlp-inference.md +++ b/explore-analyze/machine-learning/nlp/ml-nlp-inference.md @@ -14,7 +14,7 @@ After you [deploy a trained model in your cluster](ml-nlp-deploy-models.md), you ## Add an {{infer}} processor to an ingest pipeline [ml-nlp-inference-processor] -In {{kib}}, you can create and edit pipelines in **{{stack-manage-app}}** > **Ingest Pipelines**. To open **Ingest Pipelines**, find **{{stack-manage-app}}** in the main menu, or use the [global search field](../../overview/kibana-quickstart.md#_finding_your_apps_and_objects). +In {{kib}}, you can create and edit pipelines in **{{stack-manage-app}}** > **Ingest Pipelines**. To open **Ingest Pipelines**, find **{{stack-manage-app}}** in the main menu, or use the [global search field](../../find-and-organize/find-apps-and-objects.md). :::{image} ../../../images/machine-learning-ml-nlp-pipeline-lang.png :alt: Creating a pipeline in the Stack Management app @@ -142,7 +142,7 @@ POST lang-test/_doc?pipeline=my-lang-pipeline } ``` -You can also use NLP pipelines when you are reindexing documents to a new destination. For example, since the [sample web logs data set](../../overview/kibana-quickstart.md#gs-get-data-into-kibana) contain a `message` text field, you can reindex it with your {{lang-ident}} pipeline: +You can also use NLP pipelines when you are reindexing documents to a new destination. For example, since the [sample web logs data set](../../index.md#gs-get-data-into-kibana) contain a `message` text field, you can reindex it with your {{lang-ident}} pipeline: ```console POST _reindex diff --git a/explore-analyze/machine-learning/nlp/ml-nlp-ner-example.md b/explore-analyze/machine-learning/nlp/ml-nlp-ner-example.md index 63c2fa9f00..5bd9b083d6 100644 --- a/explore-analyze/machine-learning/nlp/ml-nlp-ner-example.md +++ b/explore-analyze/machine-learning/nlp/ml-nlp-ner-example.md @@ -235,7 +235,7 @@ The request returns the document marked up with one identified person: You can create a tag cloud to visualize your data processed by the {{infer}} pipeline. A tag cloud is a visualization that scales words by the frequency at which they occur. It is a handy tool for viewing the entities found in the data. -In {{kib}}, open **Stack management** > **{{data-sources-cap}}** from the main menu, or use the [global search field](../../overview/kibana-quickstart.md#_finding_your_apps_and_objects), and create a new {{data-source}} from the `les-miserables-infer` index pattern. +In {{kib}}, open **Stack management** > **{{data-sources-cap}}** from the main menu, or use the [global search field](../../find-and-organize/find-apps-and-objects.md), and create a new {{data-source}} from the `les-miserables-infer` index pattern. Open **Dashboard** and create a new dashboard. Select the **Aggregation based-type > Tag cloud** visualization. Choose the new {{data-source}} as the source. diff --git a/explore-analyze/machine-learning/setting-up-machine-learning.md b/explore-analyze/machine-learning/setting-up-machine-learning.md index 461e1a9742..c5527ce8bf 100644 --- a/explore-analyze/machine-learning/setting-up-machine-learning.md +++ b/explore-analyze/machine-learning/setting-up-machine-learning.md @@ -32,7 +32,7 @@ Assigning security privileges affects how users access {{ml-features}}. Consider You can configure these privileges -* under **Security**. To open Security, find **{{stack-manage-app}}** in the main menu or use the [global search field](../overview/kibana-quickstart.md#_finding_your_apps_and_objects). +* under **Security**. To open Security, find **{{stack-manage-app}}** in the main menu or use the [global search field](../find-and-organize/find-apps-and-objects.md). * via the respective {{es}} security APIs. ### {{es}} API user [es-security-privileges] @@ -63,16 +63,16 @@ Granting `All` or `Read` {{kib}} feature privilege for {{ml-app}} will also gran #### Feature visibility in Spaces [kib-visibility-spaces] -In {{kib}}, the {{ml-features}} must be visible in your [space](../../deploy-manage/manage-spaces.md#spaces-control-feature-visibility). To manage which features are visible in your space, go to **{{stack-manage-app}}** > **{{kib}}** > **Spaces** or use the [global search field](../overview/kibana-quickstart.md#_finding_your_apps_and_objects) to locate **Spaces** directly. +In {{kib}}, the {{ml-features}} must be visible in your [space](../../deploy-manage/manage-spaces.md#spaces-control-feature-visibility). To manage which features are visible in your space, go to **{{stack-manage-app}}** > **{{kib}}** > **Spaces** or use the [global search field](../find-and-organize/find-apps-and-objects.md) to locate **Spaces** directly. :::{image} ../../images/machine-learning-spaces.jpg :alt: Manage spaces in {kib} :class: screenshot ::: -In addition to index privileges, source {{data-sources}} must also exist in the same space as your {{ml}} jobs. You can configure these under **{{data-sources-caps}}**. To open **{{data-sources-caps}}**, find **{{stack-manage-app}}** > **{{kib}}** in the main menu, or use the [global search field](../overview/kibana-quickstart.md#_finding_your_apps_and_objects). +In addition to index privileges, source {{data-sources}} must also exist in the same space as your {{ml}} jobs. You can configure these under **{{data-sources-caps}}**. To open **{{data-sources-caps}}**, find **{{stack-manage-app}}** > **{{kib}}** in the main menu, or use the [global search field](../find-and-organize/find-apps-and-objects.md). -Each {{ml}} job and trained model can be assigned to all, one, or multiple spaces. This can be configured in **Machine Learning**. To open **Machine Learning**, find **{{stack-manage-app}} > Alerts and Insights** in the main menu, or use the [global search field](../overview/kibana-quickstart.md#_finding_your_apps_and_objects). You can edit the spaces that a job or model is assigned to by clicking the icons in the **Spaces** column. +Each {{ml}} job and trained model can be assigned to all, one, or multiple spaces. This can be configured in **Machine Learning**. To open **Machine Learning**, find **{{stack-manage-app}} > Alerts and Insights** in the main menu, or use the [global search field](../find-and-organize/find-apps-and-objects.md). You can edit the spaces that a job or model is assigned to by clicking the icons in the **Spaces** column. :::{image} ../../images/machine-learning-assign-job-spaces.jpg :alt: Assign machine learning jobs to spaces diff --git a/explore-analyze/overview/kibana-quickstart.md b/explore-analyze/overview/kibana-quickstart.md deleted file mode 100644 index 9daf178a44..0000000000 --- a/explore-analyze/overview/kibana-quickstart.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -mapped_urls: - - https://www.elastic.co/guide/en/kibana/current/get-started.html - - https://www.elastic.co/guide/en/kibana/current/kibana-concepts-analysts.html ---- - -# Kibana quickstart - -% What needs to be done: Refine - -% Use migrated content from existing pages that map to this page: - -% - [ ] ./raw-migrated-files/kibana/kibana/get-started.md -% - [ ] ./raw-migrated-files/kibana/kibana/kibana-concepts-analysts.md - -% Internal links rely on the following IDs being on this page (e.g. as a heading ID, paragraph ID, etc): - -$$$gs-get-data-into-kibana$$$ - -$$$_finding_your_apps_and_objects$$$ - -$$$semi-structured-search$$$ - -$$$set-up-on-cloud$$$ - -$$$kibana-concepts-searching-your-data$$$ - -$$$explore-the-data$$$ - -$$$view-and-analyze-the-data$$$ \ No newline at end of file diff --git a/explore-analyze/overview/kibana-quickstart/accessibility-in-kibana.md b/explore-analyze/overview/kibana-quickstart/accessibility-in-kibana.md deleted file mode 100644 index c511b82b25..0000000000 --- a/explore-analyze/overview/kibana-quickstart/accessibility-in-kibana.md +++ /dev/null @@ -1,69 +0,0 @@ ---- -navigation_title: "Accessibility" -mapped_pages: - - https://www.elastic.co/guide/en/kibana/current/accessibility.html ---- - - - -# Accessibility in Kibana [accessibility] - - -Elastic is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience, and strive toward ensuring our tools are usable by everyone. - - -## Measures to support accessibility [accessibility-measures] - -Elastic takes the following measures to ensure accessibility of Kibana: - -* Maintains and incorporates an [accessible component library](https://elastic.github.io/eui/). -* Provides continual accessibility training for our staff. -* Employs a third-party audit. - - -## Conformance status [accessibility-conformance-status] - -Kibana aims to meet [WCAG 2.1 level AA](https://www.w3.org/WAI/WCAG21/quickref/?currentsidebar=%23col_customize&levels=aaa&technologies=server%2Csmil%2Cflash%2Csl) compliance. Currently, we can only claim to partially conform, meaning we do not fully meet all of the success criteria. However, we do try to take a broader view of accessibility, and go above and beyond the legal and regulatory standards to provide a good experience for all of our users. - - -## Feedback [accessibility-feedback] - -We welcome your feedback on the accessibility of Kibana. Please let us know if you encounter accessibility barriers on Kibana by either emailing us at `accessibility@elastic.co` or opening [an issue on GitHub](https://github.com/elastic/kibana/issues/new?labels=Project%3AAccessibility&template=Accessibility.md&title=%28Accessibility%29). - - -## Technical specifications [accessibility-specs] - -Accessibility of Kibana relies on the following technologies to work with your web browser and any assistive technologies or plugins installed on your computer: - -* HTML -* CSS -* JavaScript -* WAI-ARIA - - -## Limitations and alternatives [accessibility-limitations-and-alternatives] - -Despite our best efforts to ensure accessibility of Kibana, there are some limitations. Please [open an issue on GitHub](https://github.com/elastic/kibana/issues/new?labels=Project%3AAccessibility&template=Accessibility.md&title=%28Accessibility%29) if you observe an issue not in this list. - -Known limitations are in the following areas: - -* **Charts**: We have a clear plan for the first steps of making charts accessible. We’ve opened this [Charts accessibility ticket on GitHub](https://github.com/elastic/elastic-charts/issues/300) for tracking our progress. -* **Maps**: Maps might pose difficulties to users with vision disabilities. We welcome your input on making our maps accessible. Go to the [Maps accessibility ticket on GitHub](https://github.com/elastic/kibana/issues/57271) to join the discussion and view our plans. -* **Tables**: Although generally accessible and marked-up as standard HTML tables with column headers, tables rarely make use of row headers and have poor captions. You will see incremental improvements as various applications adopt a new accessible component. -* **Color contrast**: Modern Kibana interfaces generally do not have color contrast issues. However, older code might fall below the recommended contrast levels. As we continue to update our code, this issue will phase out naturally. - -To see individual tickets, view our [GitHub issues with label "`Project:Accessibility`"](https://github.com/elastic/kibana/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3AProject%3AAccessibility). - - -## Assessment approach [accessibility-approach] - -Elastic assesses the accessibility of Kibana with the following approaches: - -* **Self-evaluation**: Our employees are familiar with accessibility standards and review new designs and implemented features to confirm that they are accessible. -* **External evaluation**: We engage external contractors to help us conduct an independent assessment and generate a formal VPAT. Please email `accessibility@elastic.co` if you’d like a copy. -* **Automated evaluation**: We are starting to run [axe](https://www.deque.com/axe/) on every page. See our current progress in the [automated testing GitHub issue](https://github.com/elastic/kibana/issues/51456). - -Manual testing largely focuses on screen reader support and is done on: - -* VoiceOver on MacOS with Safari, Chrome and Edge -* NVDA on Windows with Chrome and Firefox diff --git a/explore-analyze/query-filter.md b/explore-analyze/query-filter.md index c03d2d2d35..29525c6537 100644 --- a/explore-analyze/query-filter.md +++ b/explore-analyze/query-filter.md @@ -7,6 +7,10 @@ mapped_pages: You can use {{es}} as a basic document store to retrieve documents and their metadata. However, the real power of {{es}} comes from its advanced search and analytics capabilities. +* **{{es}} makes JSON documents searchable and aggregatable.** The documents are stored in an [index](/manage-data/data-store/index-basics.md) or [data stream](/manage-data/data-store/index-types/data-streams.md), which represent one type of data. +* ***Searchable* means that you can filter the documents for conditions.** For example, you can filter for data "within the last 7 days" or data that "contains the word {{kib}}". {{kib}} provides many ways for you to construct filters, which are also called queries or search terms. +* ***Aggregatable* means that you can extract summaries from matching documents.** The simplest aggregation is **count**, and it is frequently used in combination with the **date histogram**, to see count over time. The **terms** aggregation shows the most frequent values. + ## Querying You’ll use a combination of an API endpoint and a query language to interact with your data. diff --git a/explore-analyze/query-filter/languages/kql.md b/explore-analyze/query-filter/languages/kql.md index f01d5d425f..4d5b9b7e75 100644 --- a/explore-analyze/query-filter/languages/kql.md +++ b/explore-analyze/query-filter/languages/kql.md @@ -13,6 +13,20 @@ The {{kib}} Query Language (KQL) is a simple text-based query language for filte Use KQL to filter documents where a value for a field exists, matches a given value, or is within a given range. +## Semi-structured search [semi-structured-search] + +Combine free text search with field-based search using KQL. Type a search term to match across all fields, or start typing a field name to get suggestions for field names and operators that you can use to build a structured query. The semi-structured search will filter documents for matches, and only return matching documents. + +| | | +| --- | --- | +| Exact phrase query | `http.response.body.content.text:"quick brown fox"` | +| Terms query | http.response.status_code:400 401 404 | +| Boolean query | `response:200 or extension:php` | +| Range query | `account_number >= 100 and items_sold <= 200` | +| Wildcard query | `machine.os:win*` | + + + ## Filter for documents where a field exists [_filter_for_documents_where_a_field_exists] To filter documents for which an indexed value exists for a given field, use the `*` operator. For example, to filter for documents where the `http.request.method` field exists, use the following syntax: diff --git a/explore-analyze/query-filter/tools/console.md b/explore-analyze/query-filter/tools/console.md index 718fe11a3d..effa226ef5 100644 --- a/explore-analyze/query-filter/tools/console.md +++ b/explore-analyze/query-filter/tools/console.md @@ -30,7 +30,7 @@ $$$import-export-console-requests$$$ :class: screenshot ::: -To go to **Console**, find **Dev Tools** in the navigation menu or use the [global search bar](../../../get-started/the-stack.md#kibana-navigation-search). +To go to **Console**, find **Dev Tools** in the navigation menu or use the [global search bar](/explore-analyze/find-and-organize/find-apps-and-objects.md). You can also find Console directly on certain Search solution and Elasticsearch serverless project pages, where you can expand it from the footer. This Console, called **Persistent Console**, has the same capabilities and shares the same history as the Console in **Dev Tools**. diff --git a/explore-analyze/query-filter/tools/grok-debugger.md b/explore-analyze/query-filter/tools/grok-debugger.md index 58fd99d5c5..15019246c1 100644 --- a/explore-analyze/query-filter/tools/grok-debugger.md +++ b/explore-analyze/query-filter/tools/grok-debugger.md @@ -23,7 +23,7 @@ If you’re using {{stack-security-features}}, you must have the `manage_pipelin :::: -1. Find the **Grok Debugger** by navigating to the **Developer tools** page using the navigation menu or the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find the **Grok Debugger** by navigating to the **Developer tools** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. In **Sample Data**, enter a message that is representative of the data that you want to parse. For example: ```ruby diff --git a/explore-analyze/query-filter/tools/search-profiler.md b/explore-analyze/query-filter/tools/search-profiler.md index 6554932796..6e069b765e 100644 --- a/explore-analyze/query-filter/tools/search-profiler.md +++ b/explore-analyze/query-filter/tools/search-profiler.md @@ -12,7 +12,7 @@ The **{{searchprofiler}}** tool can transform this JSON output into a visualizat ## Get started [search-profiler-getting-started] -Find the **{{searchprofiler}}** by navigating to the **Developer tools** page using the navigation menu or the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +Find the **{{searchprofiler}}** by navigating to the **Developer tools** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). **{{searchprofiler}}** displays the names of the indices searched, the shards in each index, and how long it took for the query to complete. To try it out, replace the default `match_all` query with the query you want to profile, and then click **Profile**. diff --git a/explore-analyze/report-and-share.md b/explore-analyze/report-and-share.md index a8eef07cc6..0962c085b3 100644 --- a/explore-analyze/report-and-share.md +++ b/explore-analyze/report-and-share.md @@ -136,7 +136,7 @@ For more information on using Elasticsearch APIs directly, see [Scroll API](http We recommend using PNG/PDF reports to export moderate amounts of data only. The feature enables a high-level export capability, but it’s not intended for bulk export. If you need to export several pages of image data, consider using multiple report jobs to export a small number of pages at a time. If the screenshot of exported dashboard contains a large number of pixels, consider splitting the large dashboard into smaller artifacts to use less memory and CPU resources. -For the most reliable configuration of PDF/PNG {{report-features}}, consider installing {{kib}} using [Docker](/deploy-manage/deploy/self-managed/install-with-docker.md) or using [Elastic Cloud](/explore-analyze/overview/kibana-quickstart.md#set-up-on-cloud). +For the most reliable configuration of PDF/PNG {{report-features}}, consider installing {{kib}} using [Docker](/deploy-manage/deploy/self-managed/install-with-docker.md) or using [Elastic Cloud](https://cloud.elastic.co). ## Create JSON files [download-as-json] diff --git a/explore-analyze/report-and-share/reporting-troubleshooting-pdf.md b/explore-analyze/report-and-share/reporting-troubleshooting-pdf.md index 1f33ef2575..1a6a74aa09 100644 --- a/explore-analyze/report-and-share/reporting-troubleshooting-pdf.md +++ b/explore-analyze/report-and-share/reporting-troubleshooting-pdf.md @@ -12,7 +12,7 @@ mapped_pages: ::::{note} We recommend using PNG/PDF reports to export moderate amounts of data only. The feature enables a high-level export capability, but it’s not intended for bulk export. If you need to export several pages of image data, consider using multiple report jobs to export a small number of pages at a time. If the screenshot of exported dashboard contains a large number of pixels, consider splitting the large dashboard into smaller artifacts to use less memory and CPU resources. -For the most reliable configuration of PDF/PNG {{report-features}}, consider installing {{kib}} using [Docker](../../deploy-manage/deploy/self-managed/install-with-docker.md) or using [Elastic Cloud](../overview/kibana-quickstart.md#set-up-on-cloud). +For the most reliable configuration of PDF/PNG {{report-features}}, consider installing {{kib}} using [Docker](../../deploy-manage/deploy/self-managed/install-with-docker.md) or using [Elastic Cloud](https://cloud.elastic.co). :::: diff --git a/explore-analyze/scripting/painless-lab.md b/explore-analyze/scripting/painless-lab.md index 210347a9a3..c11c52726e 100644 --- a/explore-analyze/scripting/painless-lab.md +++ b/explore-analyze/scripting/painless-lab.md @@ -12,7 +12,7 @@ This functionality is in beta and is subject to change. The design and code is l The **Painless Lab** is an interactive code editor that lets you test and debug [Painless scripts](modules-scripting-painless.md) in real-time. You can use the Painless scripting language to create [{{kib}} runtime fields](../find-and-organize/data-views.md#runtime-fields), process [reindexed data](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-reindex.html), define complex [Watcher conditions](../alerts-cases/watcher.md#watcher-create-advanced-watch), and work with data in other contexts. -Find **Painless Lab** by navigating to the **Developer tools** page using the navigation menu or the [global search field](../../get-started/the-stack.md#kibana-navigation-search). +Find **Painless Lab** by navigating to the **Developer tools** page using the navigation menu or the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md). :::{image} ../../images/kibana-painless-lab.png :alt: Painless Lab diff --git a/explore-analyze/toc.yml b/explore-analyze/toc.yml index 80d8488f5e..cb10bceb41 100644 --- a/explore-analyze/toc.yml +++ b/explore-analyze/toc.yml @@ -1,9 +1,6 @@ project: 'Explore and analyze' toc: - file: index.md - - file: overview/kibana-quickstart.md - children: - - file: overview/kibana-quickstart/accessibility-in-kibana.md - file: query-filter.md children: - file: query-filter/languages.md diff --git a/explore-analyze/visualize/canvas.md b/explore-analyze/visualize/canvas.md index 2bb6298e74..92c36fe216 100644 --- a/explore-analyze/visualize/canvas.md +++ b/explore-analyze/visualize/canvas.md @@ -35,7 +35,7 @@ To create workpads, you must meet the minimum requirements. * Have an understanding of [{{es}} documents and indices](../../manage-data/data-store/index-basics.md). * Make sure you have sufficient privileges to create and save workpads. When the read-only indicator appears, you have insufficient privileges, and the options to create and save workpads are unavailable. For more information, refer to [Granting access to {{kib}}](../../deploy-manage/users-roles/cluster-or-deployment-auth/built-in-roles.md). -You can open **Canvas** using the navigation menu or the [global search field](../../get-started/the-stack.md#kibana-navigation-search). +You can open **Canvas** using the navigation menu or the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md). ### Start with a blank workpad [start-with-a-blank-workpad] @@ -71,7 +71,7 @@ On the **Canvas** page, drag the file to the **Import workpad JSON file** field. Each of the {{kib}} sample data sets comes with a workpad that you can use for your own workpad inspiration. -1. Add a [sample data set](../overview/kibana-quickstart.md#gs-get-data-into-kibana). +1. Add a [sample data set](../index.md#gs-get-data-into-kibana). 2. On a sample data card, click **View data**, then select **Canvas**. diff --git a/explore-analyze/visualize/canvas/canvas-tutorial.md b/explore-analyze/visualize/canvas/canvas-tutorial.md index 436056ca78..4e89a4db3d 100644 --- a/explore-analyze/visualize/canvas/canvas-tutorial.md +++ b/explore-analyze/visualize/canvas/canvas-tutorial.md @@ -12,8 +12,8 @@ To familiarize yourself with **Canvas**, add the Sample eCommerce orders data, t To create a workpad of the eCommerce store data, add the data set, then create the workpad. -1. [Install the eCommerce sample data](../../overview/kibana-quickstart.md#gs-get-data-into-kibana). -2. Go to **Canvas** using the navigation menu or the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. [Install the eCommerce sample data](../../index.md#gs-get-data-into-kibana). +2. Go to **Canvas** using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 3. Select **Create workpad**. diff --git a/explore-analyze/visualize/custom-visualizations-with-vega.md b/explore-analyze/visualize/custom-visualizations-with-vega.md index 4b2f63fe8d..b092481890 100644 --- a/explore-analyze/visualize/custom-visualizations-with-vega.md +++ b/explore-analyze/visualize/custom-visualizations-with-vega.md @@ -43,7 +43,7 @@ As you edit the specs, work in small steps, and frequently save your work. Small Before starting, add the eCommerce sample data that you’ll use in your spec, then create the dashboard. -1. [Install the eCommerce sample data set](../overview/kibana-quickstart.md#gs-get-data-into-kibana). +1. [Install the eCommerce sample data set](../index.md#gs-get-data-into-kibana). 2. Go to **Dashboards**. 3. On the **Dashboards** page, click **Create dashboard**. @@ -84,7 +84,7 @@ To create the stacked area chart, add the aggregations. To check your work, open and use the [**Console**](../query-filter/tools/console.md) on a separate browser tab. 1. Open {{kib}} on a new tab. -2. Go to the **Developer tools** page using the navigation menu or the [global search field](../../get-started/the-stack.md#kibana-navigation-search). +2. Go to the **Developer tools** page using the navigation menu or the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md). 3. On the **Console** editor, enter the aggregation, then click **Click to send request**: ```js diff --git a/explore-analyze/visualize/image-panels.md b/explore-analyze/visualize/image-panels.md index 8f3f9a3a66..0da6727bac 100644 --- a/explore-analyze/visualize/image-panels.md +++ b/explore-analyze/visualize/image-panels.md @@ -24,7 +24,7 @@ You can upload images from your computer, select previously uploaded images, or :class: screenshot ::: -To manage your uploaded image files, go to the **Files** management page using the navigation menu or the [global search field](../../get-started/the-stack.md#kibana-navigation-search). +To manage your uploaded image files, go to the **Files** management page using the navigation menu or the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md). ::::{warning} When you export a dashboard, the uploaded image files are not exported. When importing a dashboard with an image panel, and the image file is unavailable, the image panel displays a `not found` warning. Such panels have to be fixed manually by re-uploading the image using the panel’s image editor. diff --git a/explore-analyze/visualize/legacy-editors/aggregation-based.md b/explore-analyze/visualize/legacy-editors/aggregation-based.md index d5a9573488..25ff645462 100644 --- a/explore-analyze/visualize/legacy-editors/aggregation-based.md +++ b/explore-analyze/visualize/legacy-editors/aggregation-based.md @@ -74,7 +74,7 @@ You collected data from your web server, and you want to visualize and analyze t Add the sample web logs data that you’ll use to create the bar chart, then create the dashboard. -1. [Install the web logs sample data set](../../overview/kibana-quickstart.md#gs-get-data-into-kibana). +1. [Install the web logs sample data set](../../index.md#gs-get-data-into-kibana). 2. Go to **Dashboards**. 3. On the **Dashboards** page, click **Create dashboard**. diff --git a/explore-analyze/visualize/lens.md b/explore-analyze/visualize/lens.md index c6c8906ba3..165a3139af 100644 --- a/explore-analyze/visualize/lens.md +++ b/explore-analyze/visualize/lens.md @@ -228,7 +228,7 @@ Annotations allow you to call out specific points in your visualizations that ar Annotations support two placement types: * **Static date** — Displays annotations for specific times or time ranges. -* **Custom query** — Displays annotations based on custom {{es}} queries. For detailed information about queries, check [Semi-structured search](../overview/kibana-quickstart.md#semi-structured-search). +* **Custom query** — Displays annotations based on custom {{es}} queries. For detailed information about queries, check [Semi-structured search](/explore-analyze/query-filter/languages/kql.md#semi-structured-search). Any annotation layer can be saved as an annotation group to the **Visualize Library** in order to reuse it in other visualizations. Any changes made to the annotation group will be reflected in all visualizations to which it is added. @@ -253,7 +253,7 @@ Create custom query annotations. 1. Select **Custom query**. 2. Enter the **Annotation query** for the data you want to display. - For detailed information about queries and examples, check [Semi-structured search](../overview/kibana-quickstart.md#semi-structured-search). + For detailed information about queries and examples, check [Semi-structured search](/explore-analyze/query-filter/languages/kql.md#semi-structured-search). 3. Select the **Target date field**. @@ -299,7 +299,7 @@ For example, to track the number of bytes in the 75th percentile, add a shaded * ### Apply filters [filter-the-data] -You can use the [query bar](../overview/kibana-quickstart.md#semi-structured-search) to create queries that filter all the data in a visualization, or use the layer pane and legend filters to apply filters based on field values. +You can use the query bar to create queries that filter all the data in a visualization, or use the layer pane and legend filters to apply filters based on field values. #### Apply multiple KQL filters [filter-with-the-function] diff --git a/explore-analyze/visualize/maps/asset-tracking-tutorial.md b/explore-analyze/visualize/maps/asset-tracking-tutorial.md index 409955f18e..2ce4f54a8b 100644 --- a/explore-analyze/visualize/maps/asset-tracking-tutorial.md +++ b/explore-analyze/visualize/maps/asset-tracking-tutorial.md @@ -39,7 +39,7 @@ To get to the fun of visualizing and alerting on Portland public transport vehic ### Step 1: Set up an Elasticsearch index [_step_1_set_up_an_elasticsearch_index] -1. In Kibana, go to **Developer tools** using the navigation menu or the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. In Kibana, go to **Developer tools** using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. In **Console**, create the `tri_met_tracks` index lifecyle policy. This policy will keep the events in the hot data phase for 7 days. The data then moves to the warm phase. After 365 days in the warm phase, the data is deleted. ::::{dropdown} ILM policy definition diff --git a/explore-analyze/visualize/maps/maps-getting-started.md b/explore-analyze/visualize/maps/maps-getting-started.md index db4ec8bb93..af66b1af80 100644 --- a/explore-analyze/visualize/maps/maps-getting-started.md +++ b/explore-analyze/visualize/maps/maps-getting-started.md @@ -25,7 +25,7 @@ When you complete this tutorial, you’ll have a map that looks like this: ## Prerequisites [_prerequisites_2] * If you don’t already have {{kib}}, set it up with [our free trial](https://www.elastic.co/cloud/elasticsearch-service/signup?baymax=docs-body&elektra=docs). -* This tutorial requires the [web logs sample data set](../../overview/kibana-quickstart.md). The sample data includes a [Logs] Total Requests and Bytes map, which you’ll re-create in this tutorial. +* This tutorial requires the [web logs sample data set](/explore-analyze/index.md#gs-get-data-into-kibana). The sample data includes a [Logs] Total Requests and Bytes map, which you’ll re-create in this tutorial. * You must have the correct privileges for creating a map. If you don’t have sufficient privileges to create or save maps, a read-only icon appears in the toolbar. For more information, refer to [Granting access to {{kib}}](../../../deploy-manage/users-roles/cluster-or-deployment-auth/built-in-roles.md). diff --git a/explore-analyze/visualize/maps/maps-search.md b/explore-analyze/visualize/maps/maps-search.md index bf872fcf19..438a45f532 100644 --- a/explore-analyze/visualize/maps/maps-search.md +++ b/explore-analyze/visualize/maps/maps-search.md @@ -27,7 +27,7 @@ Only layers requesting data from {{es}} are narrowed by global search and global ## Narrow layers by global search [maps-narrow-layer-by-global-search] -Layers that request data from {{es}} are narrowed when you submit a [search](../../overview/kibana-quickstart.md#kibana-concepts-searching-your-data). Layers narrowed by semi-structured search and filters contain the filter icon ![filter icon](../../../images/kibana-filter_icon.png "") next to the layer name in the legend. +Layers that request data from {{es}} are narrowed when you submit a search. Layers narrowed by semi-structured search and filters contain the filter icon ![filter icon](../../../images/kibana-filter_icon.png "") next to the layer name in the legend. To prevent the global search from applying to a layer, configure the following: diff --git a/explore-analyze/visualize/maps/reverse-geocoding-tutorial.md b/explore-analyze/visualize/maps/reverse-geocoding-tutorial.md index 6d7dfac373..821588353e 100644 --- a/explore-analyze/visualize/maps/reverse-geocoding-tutorial.md +++ b/explore-analyze/visualize/maps/reverse-geocoding-tutorial.md @@ -29,9 +29,7 @@ When you complete this tutorial, you’ll have a map that looks like this: GeoIP is a common way of transforming an IP address to a longitude and latitude. GeoIP is roughly accurate on the city level globally and neighborhood level in selected countries. It’s not as good as an actual GPS location from your phone, but it’s much more precise than just a country, state, or province. -You’ll use the [web logs sample data set](../../overview/kibana-quickstart.md) that comes with Kibana for this tutorial. Web logs sample data set has longitude and latitude. If your web log data does not contain longitude and latitude, use [GeoIP processor](https://www.elastic.co/guide/en/elasticsearch/reference/current/geoip-processor.html) to transform an IP address into a [geo_point](https://www.elastic.co/guide/en/elasticsearch/reference/current/geo-point.html) field. - -To install the web logs sample data set, refer to [Add sample data](../../overview/kibana-quickstart.md#gs-get-data-into-kibana). +You’ll use the [web logs sample data set](../../index.md#gs-get-data-into-kibana) that comes with Kibana for this tutorial. Web logs sample data set has longitude and latitude. If your web log data does not contain longitude and latitude, use [GeoIP processor](https://www.elastic.co/guide/en/elasticsearch/reference/current/geoip-processor.html) to transform an IP address into a [geo_point](https://www.elastic.co/guide/en/elasticsearch/reference/current/geo-point.html) field. ## Step 2: Index Combined Statistical Area (CSA) regions [_step_2_index_combined_statistical_area_csa_regions] @@ -76,7 +74,7 @@ Looking at the map, you get a sense of what constitutes a metro area in the eyes To visualize CSA regions by web log traffic, the web log traffic must contain a CSA region identifier. You’ll use {{es}} [enrich processor](https://www.elastic.co/guide/en/elasticsearch/reference/current/enrich-processor.html) to add CSA region identifiers to the web logs sample data set. You can skip this step if your source data already contains region identifiers. -1. Go to **Developer tools** using the navigation menu or the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Go to **Developer tools** using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. In **Console**, create a [geo_match enrichment policy](../../../manage-data/ingest/transform-enrich/example-enrich-data-based-on-geolocation.md): ```js diff --git a/get-started/introduction.md b/get-started/introduction.md index bfd9467b36..0693fb7e45 100644 --- a/get-started/introduction.md +++ b/get-started/introduction.md @@ -33,7 +33,7 @@ Being able to search, observe, and protect your data is a requirement for any an ## Analyze [visualize-and-analyze] -With {{kib}} [**Analytics**](../explore-analyze/overview/kibana-quickstart.md), you can quickly search through large amounts of data, explore fields and values, and then use the drag-and-drop interface to rapidly build charts, tables, metrics, and more. +With {{kib}} [**Analytics**](/explore-analyze/index.md), you can quickly search through large amounts of data, explore fields and values, and then use the drag-and-drop interface to rapidly build charts, tables, metrics, and more. :::{image} ../images/kibana-visualization-journey.png :alt: User data analysis journey diff --git a/raw-migrated-files/cloud/cloud-enterprise/ece-create-deployment.md b/raw-migrated-files/cloud/cloud-enterprise/ece-create-deployment.md index 43ea1d5cd7..df50435001 100644 --- a/raw-migrated-files/cloud/cloud-enterprise/ece-create-deployment.md +++ b/raw-migrated-files/cloud/cloud-enterprise/ece-create-deployment.md @@ -38,7 +38,7 @@ If these system templates are not suitable for your use case, you can [create yo While waiting, you are prompted to save the admin credentials for your deployment which provides you with superuser access to Elasticsearch. Write down the password for the `elastic` user (or the `admin` user for version 2.x) and keep it somewhere safe. These credentials also help you [add data using Kibana](../../../manage-data/ingest.md). If you need to refresh these credentials, you can [reset the password](../../../deploy-manage/users-roles/cluster-or-deployment-auth/built-in-users.md). -5. Once the deployment is ready, select **Continue** to open the deployment’s main page. From here, you can start ingesting data or simply [try a sample data](../../../explore-analyze/overview/kibana-quickstart.md#gs-get-data-into-kibana) set to get started. +5. Once the deployment is ready, select **Continue** to open the deployment’s main page. From here, you can start ingesting data or simply [try a sample data](../../../explore-analyze/index.md#gs-get-data-into-kibana) set to get started. :::{image} ../../../images/cloud-enterprise-ece-deployment-mainpage.png :alt: ECE Deployment main page diff --git a/raw-migrated-files/docs-content/serverless/ai-assistant-knowledge-base.md b/raw-migrated-files/docs-content/serverless/ai-assistant-knowledge-base.md index 3218f5ae6c..ecda0445f1 100644 --- a/raw-migrated-files/docs-content/serverless/ai-assistant-knowledge-base.md +++ b/raw-migrated-files/docs-content/serverless/ai-assistant-knowledge-base.md @@ -51,7 +51,7 @@ Knowledge Base setup may take several minutes. It will continue in the backgroun ### Option 2: Enable Knowledge Base from the Security AI settings [_option_2_enable_knowledge_base_from_the_security_ai_settings] -1. To open Security AI settings, use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search) to find "AI Assistant for Security." +1. To open Security AI settings, use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md) to find "AI Assistant for Security." 2. On the **Knowledge Base** tab, click **Setup Knowledge Base**. If the button doesn’t appear, Knowledge Base is already enabled. :::{image} ../../../images/serverless-knowledge-base-assistant-settings-kb-tab.png @@ -88,7 +88,7 @@ When you enable Knowledge Base, it comes pre-populated with articles from [Elast Add an individual document to Knowledge Base when you want AI Assistant to remember a specific piece of information. -1. To open Security AI settings, use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search) to find "AI Assistant for Security." Select the **Knowledge Base** tab. +1. To open Security AI settings, use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md) to find "AI Assistant for Security." Select the **Knowledge Base** tab. 2. Click **New → Document** and give it a name. 3. Under **Sharing**, select whether this knowledge should be **Global** or **Private**. 4. Write the knowledge AI Assistant should remember in the **Markdown text** field. @@ -121,7 +121,7 @@ Indices added to Knowledge Base must have at least one field mapped as [semantic :::: -1. To open Security AI settings, use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search) to find "AI Assistant for Security." Select the **Knowledge Base** tab. +1. To open Security AI settings, use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md) to find "AI Assistant for Security." Select the **Knowledge Base** tab. 2. Click **New → Index**. 3. Name the knowledge source. 4. Under **Sharing**, select whether this knowledge should be **Global** or **Private**. diff --git a/raw-migrated-files/docs-content/serverless/connect-to-byo-llm.md b/raw-migrated-files/docs-content/serverless/connect-to-byo-llm.md index d96d8f27f5..d4fa16bb94 100644 --- a/raw-migrated-files/docs-content/serverless/connect-to-byo-llm.md +++ b/raw-migrated-files/docs-content/serverless/connect-to-byo-llm.md @@ -194,7 +194,7 @@ You can monitor the performance of the host running LM Studio using Elastic’s Finally, configure the connector: 1. Log in to your Elastic deployment. -2. Find the **Connectors** page in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Then click **Create Connector**, and select **OpenAI**. The OpenAI connector enables this use case because LM Studio uses the OpenAI SDK. +2. Find the **Connectors** page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Then click **Create Connector**, and select **OpenAI**. The OpenAI connector enables this use case because LM Studio uses the OpenAI SDK. 3. Name your connector to help keep track of the model version you are using. 4. Under **Select an OpenAI provider**, select **Other (OpenAI Compatible Service)**. 5. Under **URL**, enter the domain name specified in your Nginx configuration file, followed by `/v1/chat/completions`. diff --git a/raw-migrated-files/docs-content/serverless/ingest-falco.md b/raw-migrated-files/docs-content/serverless/ingest-falco.md index 796b9aa164..7be40874d7 100644 --- a/raw-migrated-files/docs-content/serverless/ingest-falco.md +++ b/raw-migrated-files/docs-content/serverless/ingest-falco.md @@ -18,7 +18,7 @@ In {{elastic-sec}}: Next, to make alerts from Falco appear on {{elastic-sec}}'s **Alerts** page: -1. Find the **Detection rules (SIEM)** page in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find the **Detection rules (SIEM)** page in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Search for a rule named `External Alerts`. Install it if necessary, and enable it. diff --git a/raw-migrated-files/docs-content/serverless/slo-troubleshoot-slos.md b/raw-migrated-files/docs-content/serverless/slo-troubleshoot-slos.md index c5214a6e5e..0870ecc1cf 100644 --- a/raw-migrated-files/docs-content/serverless/slo-troubleshoot-slos.md +++ b/raw-migrated-files/docs-content/serverless/slo-troubleshoot-slos.md @@ -129,7 +129,7 @@ As mentioned, maintaining a healthy cluster is crucial for SLOs to function corr To be able to inspect SLOs you have to activate the corresponding feature in {{kib}}: -1. Open **Advanced Settings**, by finding **Stack Management** in the main menu or using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Open **Advanced Settings**, by finding **Stack Management** in the main menu or using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Enable `observability:enableInspectEsQueries` setting. Afterwards visit the **SLO edit page** and click **SLO Inspect**. @@ -162,7 +162,7 @@ Before resetting the SLO, verify that the source data and queries are correctly Follow these steps to reset an SLO: -1. Find **SLOs** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **SLOs** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click on the SLO to reset. 3. Select **Actions** → **Reset**. diff --git a/raw-migrated-files/kibana/kibana/console-kibana.md b/raw-migrated-files/kibana/kibana/console-kibana.md index a077bd877e..2a00541d87 100644 --- a/raw-migrated-files/kibana/kibana/console-kibana.md +++ b/raw-migrated-files/kibana/kibana/console-kibana.md @@ -7,7 +7,7 @@ :class: screenshot ::: -To go to **Console***, find ***Dev Tools** in the navigation menu or use the [global search bar](../../../get-started/the-stack.md#kibana-navigation-search). +To go to **Console***, find ***Dev Tools** in the navigation menu or use the [global search bar](/explore-analyze/find-and-organize/find-apps-and-objects.md). You can also find Console directly on certain Search solution and Elasticsearch serverless project pages, where you can expand it from the footer. This Console, called **Persistent Console***, has the same capabilities and shares the same history as the Console in ***Dev Tools**. diff --git a/raw-migrated-files/kibana/kibana/data-rollups.md b/raw-migrated-files/kibana/kibana/data-rollups.md index f6d1a868bd..bfa454b541 100644 --- a/raw-migrated-files/kibana/kibana/data-rollups.md +++ b/raw-migrated-files/kibana/kibana/data-rollups.md @@ -9,7 +9,7 @@ Rollups are deprecated and will be removed in a future version. Use [downsamplin A rollup job is a periodic task that aggregates data from indices specified by an index pattern, and then rolls it into a new index. Rollup indices are a good way to compactly store months or years of historical data for use in visualizations and reports. -You can go to the **Rollup Jobs** page using the navigation menu or the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +You can go to the **Rollup Jobs** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). :::{image} ../../../images/kibana-management_rollup_list.png :alt: List of currently active rollup jobs @@ -23,7 +23,7 @@ Before using this feature, you should be familiar with how rollups work. [Rollin The `manage_rollup` cluster privilege is required to access **Rollup jobs**. -To add the privilege, go to the **Roles** management page using the navigation menu or the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +To add the privilege, go to the **Roles** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). ## Create a rollup job [create-and-manage-rollup-job] @@ -90,7 +90,7 @@ You can now use the rolled up data for analysis at a fraction of the storage cos Your next step is to visualize your rolled up data in a vertical bar chart. Most visualizations support rolled up data, with the exception of Timelion and Vega visualizations. -1. Go to the **Data Views** page using the navigation menu or the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Go to the **Data Views** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Create data view**, and select **Rollup data view** from the dropdown. 3. Enter **rollup_logstash,kibana_sample_logs** as your **Data View** and `@timestamp` as the **Time Filter field name**. diff --git a/raw-migrated-files/kibana/kibana/get-started.md b/raw-migrated-files/kibana/kibana/get-started.md deleted file mode 100644 index 36afe6416c..0000000000 --- a/raw-migrated-files/kibana/kibana/get-started.md +++ /dev/null @@ -1,167 +0,0 @@ -# Quick start [get-started] - -To quickly get up and running with {{kib}}, set up on Cloud, then add a sample data set that you can explore and visualize. - -When you’re done, you’ll know how to: - -* [Explore the data with **Discover**.](../../../explore-analyze/overview/kibana-quickstart.md#explore-the-data) -* [Visualize the data with **Dashboard**.](../../../explore-analyze/overview/kibana-quickstart.md#view-and-analyze-the-data) - - -### Required privileges [_required_privileges] - -You must have `read`, `write`, and `manage` privileges on the `kibana_sample_data_*` indices. Learn how to [secure access to {{kib}}](../../../deploy-manage/users-roles/cluster-or-deployment-auth/quickstart.md), or refer to [Security privileges](../../../deploy-manage/users-roles/cluster-or-deployment-auth/elasticsearch-privileges.md) for more information. - - -## Set up on cloud [set-up-on-cloud] - -There’s no faster way to get started than with our hosted {{ess}} on Elastic Cloud: - -1. [Get a free trial](https://cloud.elastic.co/registration?page=docs&placement=docs-body). -2. Log into [Elastic Cloud](https://cloud.elastic.co?page=docs&placement=docs-body). -3. Click **Create deployment**. -4. Give your deployment a name. -5. Click **Create deployment** and download the password for the `elastic` user. - -That’s it! Now that you are up and running, it’s time to get some data into {{kib}}. {{kib}} will open as soon as your deployment is ready. - - -## Add sample data [gs-get-data-into-kibana] - -Sample data sets come with sample visualizations, dashboards, and more to help you explore {{kib}} before you ingest or add your own data. - -1. Open the **Integrations** page from the navigation menu or using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). -2. In the list of integrations, select **Sample Data**. -3. On the page that opens, select **Other sample data sets**. -4. Install the sample data sets that you want. - -Once installed, you can access the sample data in the various {{kib}} apps available to you. - - -## Explore the data [explore-the-data] - -**Discover** displays the data in an interactive histogram that shows the distribution of data, or documents, over time, and a table that lists the fields for each document that matches the {{data-source}}. To view a subset of the documents, you can apply filters to the data, and customize the table to display only the fields you want to explore. - -1. Go to **Discover**. -2. Change the [time filter](../../../explore-analyze/query-filter/filtering.md) to **Last 7 days**. - - :::{image} ../../../images/kibana-timeFilter_discover_8.4.0.png - :alt: Time filter menu with Last 7 days filter configured - :class: screenshot - ::: - -3. To view the sales orders for women’s clothing that are $60 or more, use the [**KQL**](../../../explore-analyze/query-filter/languages/kql.md) search field: - - ```text - products.taxless_price >= 60 and category : Women's Clothing - ``` - - :::{image} ../../../images/kibana-kql_discover_8.4.0.png - :alt: Discover tables that displays only the orders for women's clothing that are $60 or more - :class: screenshot - ::: - -4. To view only the product categories that contain sales orders, hover over the **category** field, then click **+**. - - :::{image} ../../../images/kibana-availableFields_discover_8.4.0.png - :alt: Discover table that displays only the product categories that contain orders - :class: screenshot - ::: - - - -## Visualize the data [view-and-analyze-the-data] - -A dashboard is a collection of panels that you can use to visualize the data. Panels contain visualizations, interactive controls, text, and more. - -1. Go to **Dashboards**. -2. Click **[eCommerce] Revenue Dashboard**. - - :::{image} ../../../images/kibana-dashboard_ecommerceRevenueDashboard_8.6.0.png - :alt: The [eCommerce] Revenue Dashboard that comes with the Sample eCommerce order data set - :class: screenshot - ::: - - - -### Create a visualization panel [create-a-visualization] - -Create a treemap visualization panel that shows the top sales regions and manufacturers, then add the panel to the dashboard. - -1. In the toolbar, click **Edit**. -2. On the dashboard, click **Create visualization**. -3. In the drag-and-drop visualization editor, open the **Visualization type** dropdown, then select **Treemap**. - - :::{image} ../../../images/kibana-visualizationTypeDropdown_lens_8.4.0.png - :alt: Chart type menu with Treemap selected - :class: screenshot - ::: - -4. From the **Available fields** list, drag the following fields to the workspace: - - * **geoip.city_name** - * **manufacturer.keyword** - - :::{image} ../../../images/kibana-ecommerceTreemap_lens_8.4.0.png - :alt: Treemap that displays Top values of geoip.city_name and Top values or manufacturer.keyword fields - :class: screenshot - ::: - -5. Click **Save and return**. - - The treemap appears as the last visualization panel on the dashboard. - - - -### Interact with the data [interact-with-the-data] - -You can interact with the dashboard data using controls that allow you to apply dashboard-level filters. Interact with the **[eCommerce] Controls** panel to view the women’s clothing data from the Gnomehouse manufacturer. - -1. From the **Manufacturer** dropdown, select **Gnomehouse**. -2. From the **Category** dropdown, select **Women’s Clothing**. - - :::{image} ../../../images/kibana-sampleDataFilter_dashboard_8.6.0.png - :alt: The [eCommerce] Revenue Dashboard that shows only the women's clothing data from the Gnomehouse manufacturer - :class: screenshot - ::: - - - -### Filter the data [filter-and-query-the-data] - -To view a subset of the data, you can apply filters to the dashboard data. Apply a filter to view the women’s clothing data generated on Wednesday from the Gnomehouse manufacturer. - -1. Click **Add filter**. - - :::{image} ../../../images/kibana-addFilter_dashboard_8.6.0.png - :alt: The Add filter action that applies dashboard-level filters - :class: screenshot - ::: - -2. From the **Field** dropdown, select **day_of_week**. -3. From the **Operator** dropdown, select **is**. -4. From the **Value** dropdown, select **Wednesday**. - - :::{image} ../../../images/kibana-addFilterOptions_dashboard_8.6.0.png - :alt: The Add filter options configured to display only the women's clothing data generated on Wednesday from the Gnomehouse manufacturer - :class: screenshot - ::: - -5. Click **Add filter**. - - :::{image} ../../../images/kibana-dashboard_sampleDataAddFilter_8.6.0.png - :alt: The [eCommerce] Revenue Dashboard that shows only the women's clothing data generated on Wednesday from the Gnomehouse manufacturer - :class: screenshot - ::: - - - -## What’s next? [quick-start-whats-next] - -**Add your own data.** Ready to add your own data? Go to [Get started with Elastic Observability](../../../solutions/observability/get-started.md), or go to [Add data to {{kib}}](../../../manage-data/ingest.md) and learn about all the ways you can add data. - -**Explore your own data in Discover.** Ready to learn more about exploring your data in **Discover**? Go to [Discover](../../../explore-analyze/discover.md). - -**Create a dashboard with your own data.** Ready to learn more about visualizing your data on a **Dashboard**? Go to [Dashboard](../../../explore-analyze/dashboards.md). - -**Try out the {{ml-features}}.** Ready to analyze the sample data sets and generate models for its patterns of behavior? Go to [Getting started with {{ml}}](../../../explore-analyze/machine-learning/anomaly-detection/ml-getting-started.md). diff --git a/raw-migrated-files/kibana/kibana/kibana-concepts-analysts.md b/raw-migrated-files/kibana/kibana/kibana-concepts-analysts.md deleted file mode 100644 index 2b061e9885..0000000000 --- a/raw-migrated-files/kibana/kibana/kibana-concepts-analysts.md +++ /dev/null @@ -1,92 +0,0 @@ -# {{kib}} concepts [kibana-concepts-analysts] - -***Learn the shared concepts for analyzing and visualizing your data*** - -As an analyst, you will use a combination of {{kib}} apps to analyze and visualize your data. {{kib}} contains both general-purpose apps and apps for the [**Enterprise Search**](https://www.elastic.co/guide/en/enterprise-search/current/index.html), [**Elastic Observability**](../../../solutions/observability/get-started/what-is-elastic-observability.md), and [**Elastic Security**](../../../solutions/security.md) solutions. These apps share a common set of concepts. - - -## Three things to know about {{es}} [_three_things_to_know_about_es] - -You don’t need to know everything about {{es}} to use {{kib}}, but the most important concepts follow: - -* **{{es}} makes JSON documents searchable and aggregatable.** The documents are stored in an [index](../../../manage-data/data-store/index-basics.md) or [data stream](../../../manage-data/data-store/index-types/data-streams.md), which represent one type of data. -* ***Searchable* means that you can filter the documents for conditions.** For example, you can filter for data "within the last 7 days" or data that "contains the word {{kib}}". {{kib}} provides many ways for you to construct filters, which are also called queries or search terms. -* ***Aggregatable* means that you can extract summaries from matching documents.** The simplest aggregation is **count**, and it is frequently used in combination with the **date histogram**, to see count over time. The **terms** aggregation shows the most frequent values. - - -## Finding your apps and objects [_finding_your_apps_and_objects] - -$$$kibana-concepts-finding-your-apps-objects$$$ -{{kib}} offers a [global search bar](../../../get-started/the-stack.md#kibana-navigation-search) on every page that you can use to find any app or saved object. Open the search bar using the keyboard shortcut Ctrl+/ on Windows and Linux, Command+/ on MacOS. - -![Global search showing matches to apps and saved objects for the word visualize](../../../images/kibana-global-search.png "") - - -## Accessing data with data views [_accessing_data_with_data_views] - -{{kib}} requires a data view to tell it which {{es}} data you want to access, and whether the data is time-based. A data view can point to one or more {{es}} data streams, indices, or index aliases by name. - -Data views are typically created by an administrator when sending data to {{es}}. You can [create or update data views](../../../explore-analyze/find-and-organize/data-views.md) in **Stack Management**, or by using a script that accesses the {{kib}} API. - -{{kib}} uses the data view to show you a list of fields, such as `event.duration`. You can customize the display name and format for each field. For example, you can tell {{kib}} to display `event.duration` in seconds. {{kib}} has [field formatters](../../../explore-analyze/find-and-organize/data-views.md#managing-fields) for strings, dates, geopoints, and numbers. - - -## Searching your data [kibana-concepts-searching-your-data] - -{{kib}} provides you several ways to build search queries, which will reduce the number of document matches that you get from {{es}}. {{kib}} apps provide a time filter, and most apps also include semi-structured search and extra filters. - -![Time filter, semi-structured search, and filters in a {{kib}} app](../../../images/kibana-top-bar.png "") - -If you frequently use any of the search options, click ![save icon](../../../images/kibana-saved-query-icon.png "") next to the semi-structured search to save or load a previously saved query. The saved query always contains the semi-structured search query, and optionally the time filter and extra filters. - - -### Time filter [_time_filter] - -The [global time filter](../../../explore-analyze/query-filter/filtering.md) limits the time range of data displayed. In most cases, the time filter applies to the time field in the data view, but some apps allow you to use a different time field. - -Using the time filter, you can configure a refresh rate to periodically resubmit your searches. - -![section of time filter where you can configure a refresh rate](../../../images/kibana-refresh-every.png "") - -To manually resubmit a search, click the **Refresh** button. This is useful when you use {{kib}} to view the underlying data. - - -### Semi-structured search [semi-structured-search] - -Combine free text search with field-based search using the Kibana Query Language (KQL). Type a search term to match across all fields, or start typing a field name to get suggestions for field names and operators that you can use to build a structured query. The semi-structured search will filter documents for matches, and only return matching documents. - -Following are some example KQL queries. For more detailed examples, refer to [Kibana Query Language](../../../explore-analyze/query-filter/languages/kql.md). - -| | | -| --- | --- | -| Exact phrase query | `http.response.body.content.text:"quick brown fox"` | -| Terms query | http.response.status_code:400 401 404 | -| Boolean query | `response:200 or extension:php` | -| Range query | `account_number >= 100 and items_sold <= 200` | -| Wildcard query | `machine.os:win*` | - - -### Additional filters with AND [autocomplete-suggestions] - -Structured filters are a more interactive way to create {{es}} queries, and are commonly used when building dashboards that are shared by multiple analysts. Each filter can be disabled, inverted, or pinned across all apps. Each of the structured filters is combined with AND logic on the rest of the query. - -![Add filter popup](../../../images/kibana-add-filter-popup.png "") - - -## Saving objects [_saving_objects] - -{{kib}} lets you save objects for your own future use or for sharing with others. Each [saved object](/explore-analyze/find-and-organize/saved-objects.md) type has different abilities. For example, you can save your search queries made with **Discover**, which lets you: - -* Share a link to your search -* Download the full search results in CSV form -* Start an aggregated visualization using the same search query -* Embed the **Discover** search results into a dashboard -* Embed the **Discover** search results into a Canvas workpad - -For organization, every saved object can have a name, [tags](../../../get-started/the-stack.md#kibana-navigation-search), and type. Use the global search to quickly open a saved object. - - -## What’s next? [_whats_next] - -* Try the {{kib}} [Quick start](../../../explore-analyze/overview/kibana-quickstart.md), which shows you how to put these concepts into action. -* Go to [Discover](../../../explore-analyze/discover.md) for instructions on searching your data. diff --git a/raw-migrated-files/kibana/kibana/osquery.md b/raw-migrated-files/kibana/kibana/osquery.md index 5fe5f782d0..b8660e0033 100644 --- a/raw-migrated-files/kibana/kibana/osquery.md +++ b/raw-migrated-files/kibana/kibana/osquery.md @@ -24,7 +24,7 @@ To use **Osquery Manager**, you must be assigned to a role with the following pr To inspect hosts, run a query against one or more agents or policies, then view the results. -1. Go to **Osquery** using the navigation menu or the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Go to **Osquery** using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. In the **Live queries** view, click **New live query**. 3. Choose to run a single query or a query pack. 4. Select one or more agents or groups to query. Start typing in the search field, and you’ll get suggestions for agents by name, ID, platform, and policy. diff --git a/raw-migrated-files/kibana/kibana/role-mappings.md b/raw-migrated-files/kibana/kibana/role-mappings.md index d908713135..46ba044a17 100644 --- a/raw-migrated-files/kibana/kibana/role-mappings.md +++ b/raw-migrated-files/kibana/kibana/role-mappings.md @@ -4,7 +4,7 @@ Role mappings are part of single sign-on (SSO), a [subscription feature](https:/ Role mappings are required when authenticating via an external identity provider, such as Active Directory, Kerberos, PKI, OIDC, or SAML. Role mappings have no effect for users inside the `native` or `file` realms. -You can find the **Role mappings** management page using the navigation menu or the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +You can find the **Role mappings** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). With **Role mappings**, you can: @@ -21,7 +21,7 @@ The `manage_security` cluster privilege is required to manage Role Mappings. ## Create a role mapping [_create_a_role_mapping] -1. Go to the **Role mappings** management page using the navigation menu or the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Go to the **Role mappings** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Create role mapping**. 3. Give your role mapping a unique name, and choose which roles you wish to assign to your users. diff --git a/raw-migrated-files/kibana/kibana/secure-reporting.md b/raw-migrated-files/kibana/kibana/secure-reporting.md index a34558f5fe..e235ff07ef 100644 --- a/raw-migrated-files/kibana/kibana/secure-reporting.md +++ b/raw-migrated-files/kibana/kibana/secure-reporting.md @@ -13,7 +13,7 @@ Kibana PNG/PDF Reporting uses a custom binary of headless Chromium, and support * Linux versions that are in end-of-life phase are not supported. * Linux systems with SELinux or fapolicyd are not supported. -Before upgrading Kibana in a production environment, we encourage you to test your screenshotting use cases in a pre-production environment to make sure your hosts support our latest build of Chromium. For the most reliable configuration of PDF/PNG {{report-features}}, consider installing {{kib}} using [Docker](../../../deploy-manage/deploy/self-managed/install-with-docker.md), or using [Elastic Cloud](../../../explore-analyze/overview/kibana-quickstart.md#set-up-on-cloud). +Before upgrading Kibana in a production environment, we encourage you to test your screenshotting use cases in a pre-production environment to make sure your hosts support our latest build of Chromium. For the most reliable configuration of PDF/PNG {{report-features}}, consider installing {{kib}} using [Docker](../../../deploy-manage/deploy/self-managed/install-with-docker.md), or using [Elastic Cloud](https://cloud.elastic.co). :::: @@ -36,7 +36,7 @@ When security is enabled, you grant users access to {{report-features}} with [{{ 1. Create the reporting role. - 1. Go to the **Roles** management page using the navigation menu or the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). + 1. Go to the **Roles** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Create role**. 2. Specify the role settings. @@ -79,7 +79,7 @@ When security is enabled, you grant users access to {{report-features}} with [{{ 4. Click **Create role**. 5. Assign the reporting role to a user. - 1. Go to the **Users** management page using the navigation menu or the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). + 1. Go to the **Users** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Select the user you want to assign the reporting role to. 3. From the **Roles** dropdown, select **custom_reporting_user**. 4. Click **Update user**. diff --git a/raw-migrated-files/kibana/kibana/tutorial-secure-access-to-kibana.md b/raw-migrated-files/kibana/kibana/tutorial-secure-access-to-kibana.md index aa47dad363..aeea767c76 100644 --- a/raw-migrated-files/kibana/kibana/tutorial-secure-access-to-kibana.md +++ b/raw-migrated-files/kibana/kibana/tutorial-secure-access-to-kibana.md @@ -50,7 +50,7 @@ Let’s work through an example together. Consider a marketing analyst who wants Create a Marketing space for your marketing analysts to use. -1. Go to the **Spaces** management page using the navigation menu or the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Go to the **Spaces** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Create a space**. 3. Give this space a unique name. For example: `Marketing`. 4. Click **Create space**. @@ -73,7 +73,7 @@ To effectively use dashboards, create a role that describes the privileges you w To create the role: -1. Go to the **Roles** management page using the navigation menu or the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Go to the **Roles** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Create role**. 3. Give this role a unique name. For example: `marketing_dashboards_role`. 4. For this example, you want to store all marketing data in the `acme-marketing-*` set of indices. To grant this access, locate the **Index privileges** section and enter: diff --git a/raw-migrated-files/kibana/kibana/using-kibana-with-security.md b/raw-migrated-files/kibana/kibana/using-kibana-with-security.md index 66906bc66e..2cdaa7e7c0 100644 --- a/raw-migrated-files/kibana/kibana/using-kibana-with-security.md +++ b/raw-migrated-files/kibana/kibana/using-kibana-with-security.md @@ -44,9 +44,9 @@ Configure roles for your {{kib}} users to control what data those users can acce 2. $$$kibana-roles$$$Create roles and users to grant access to {{kib}}. - To manage privileges in {{kib}}, go to the **Roles** management page using the navigation menu or the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). The built-in `kibana_admin` role will grant access to {{kib}} with administrator privileges. Alternatively, you can create additional roles that grant limited access to {{kib}}. + To manage privileges in {{kib}}, go to the **Roles** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). The built-in `kibana_admin` role will grant access to {{kib}} with administrator privileges. Alternatively, you can create additional roles that grant limited access to {{kib}}. - If you’re using the default native realm with Basic Authentication, go to the **Users** management page using the navigation menu or the [global search field](../../../get-started/the-stack.md#kibana-navigation-search) to create users and assign roles, or use the {{es}} [user management APIs](https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api.html#security-user-apis). For example, the following creates a user named `jacknich` and assigns it the `kibana_admin` role: + If you’re using the default native realm with Basic Authentication, go to the **Users** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md) to create users and assign roles, or use the {{es}} [user management APIs](https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api.html#security-user-apis). For example, the following creates a user named `jacknich` and assigns it the `kibana_admin` role: ```console POST /_security/user/jacknich diff --git a/raw-migrated-files/kibana/kibana/watcher-ui.md b/raw-migrated-files/kibana/kibana/watcher-ui.md index 1e1bd8edb3..e44a0c7fb1 100644 --- a/raw-migrated-files/kibana/kibana/watcher-ui.md +++ b/raw-migrated-files/kibana/kibana/watcher-ui.md @@ -2,7 +2,7 @@ Watcher is an {{es}} feature that you can use to create actions based on conditions, which are periodically evaluated using queries on your data. Watches are helpful for analyzing mission-critical and business-critical streaming data. For example, you might watch application logs for performance outages or audit access logs for security threats. -Go to the **Watcher** page using the navigation menu or the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). With this UI, you can: +Go to the **Watcher** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). With this UI, you can: * [Create a simple threshold watch](../../../explore-analyze/alerts-cases/watcher.md#watcher-create-threshold-alert) * [View your watch history and action status](../../../explore-analyze/alerts-cases/watcher.md#watcher-getting-started) diff --git a/raw-migrated-files/kibana/kibana/xpack-security.md b/raw-migrated-files/kibana/kibana/xpack-security.md index 2da1cf7c5a..95cd75f2d3 100644 --- a/raw-migrated-files/kibana/kibana/xpack-security.md +++ b/raw-migrated-files/kibana/kibana/xpack-security.md @@ -15,12 +15,12 @@ The `manage_security` cluster privilege is required to access all Security featu ## Users [_users_2] -To create and manage users, go to the **Users** management page using the navigation menu or the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). You can also change their passwords and roles. For more information about authentication and built-in users, see [Setting up user authentication](../../../deploy-manage/users-roles/cluster-or-deployment-auth/user-authentication.md). +To create and manage users, go to the **Users** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). You can also change their passwords and roles. For more information about authentication and built-in users, see [Setting up user authentication](../../../deploy-manage/users-roles/cluster-or-deployment-auth/user-authentication.md). ## Roles [_roles_2] -To manage roles, go to the **Roles** management page using the navigation menu or the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), or use the [role APIs](https://www.elastic.co/docs/api/doc/kibana/group/endpoint-roles). For more information on configuring roles for {{kib}}, see [Granting access to {{kib}}](../../../deploy-manage/users-roles/cluster-or-deployment-auth/built-in-roles.md). +To manage roles, go to the **Roles** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), or use the [role APIs](https://www.elastic.co/docs/api/doc/kibana/group/endpoint-roles). For more information on configuring roles for {{kib}}, see [Granting access to {{kib}}](../../../deploy-manage/users-roles/cluster-or-deployment-auth/built-in-roles.md). For a more holistic overview of configuring roles for the entire stack, see [User authorization](../../../deploy-manage/users-roles/cluster-or-deployment-auth/user-roles.md). diff --git a/raw-migrated-files/kibana/kibana/xpack-spaces.md b/raw-migrated-files/kibana/kibana/xpack-spaces.md index 7435fefaf0..700e993768 100644 --- a/raw-migrated-files/kibana/kibana/xpack-spaces.md +++ b/raw-migrated-files/kibana/kibana/xpack-spaces.md @@ -9,7 +9,7 @@ You can define multiple spaces in a single {{kib}} instance from the **Spaces** :class: screenshot ::: -To go to **Spaces***, find ***Stack Management** in the navigation menu or use the [global search bar](../../../get-started/the-stack.md#kibana-navigation-search). +To go to **Spaces***, find ***Stack Management** in the navigation menu or use the [global search bar](/explore-analyze/find-and-organize/find-apps-and-objects.md). ## Required privileges [_required_privileges_3] diff --git a/raw-migrated-files/observability-docs/observability/add-logs-service-name.md b/raw-migrated-files/observability-docs/observability/add-logs-service-name.md index 10a39ba94a..663953a63a 100644 --- a/raw-migrated-files/observability-docs/observability/add-logs-service-name.md +++ b/raw-migrated-files/observability-docs/observability/add-logs-service-name.md @@ -36,7 +36,7 @@ For more on defining processors, refer to [define processors](https://www.elasti For logs that with an existing field being used to represent the service name, map that field to the `service.name` field using the [alias field type](https://www.elastic.co/guide/en/elasticsearch/reference/current/field-alias.html). Follow these steps to update your mapping: -1. To open **Index Management**, find **Stack Management** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. To open **Index Management**, find **Stack Management** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Select **Index Templates**. 3. Search for the index template you want to update. 4. From the **Actions** menu for that template, select **Edit**. diff --git a/raw-migrated-files/observability-docs/observability/analyze-hosts.md b/raw-migrated-files/observability-docs/observability/analyze-hosts.md index f76e4615c6..2c0ae733e9 100644 --- a/raw-migrated-files/observability-docs/observability/analyze-hosts.md +++ b/raw-migrated-files/observability-docs/observability/analyze-hosts.md @@ -8,7 +8,7 @@ The **Hosts** page provides a metrics-driven view of your infrastructure backed * View historical data to rule out false alerts and identify root causes. * Filter and search the data to focus on the hosts you care about the most. -To open **Hosts**, find **Infrastructure** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +To open **Hosts**, find **Infrastructure** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). :::{image} ../../../images/observability-hosts.png :alt: Screenshot of the Hosts page diff --git a/raw-migrated-files/observability-docs/observability/apm-open-telemetry-collect-metrics.md b/raw-migrated-files/observability-docs/observability/apm-open-telemetry-collect-metrics.md index 742dadf33c..a618b1a8e3 100644 --- a/raw-migrated-files/observability-docs/observability/apm-open-telemetry-collect-metrics.md +++ b/raw-migrated-files/observability-docs/observability/apm-open-telemetry-collect-metrics.md @@ -64,7 +64,7 @@ Use **Discover** to validate that metrics are successfully reported to {{kib}}. -2. Find **Discover** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +2. Find **Discover** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 3. Select `apm-*` as your index pattern. 4. Filter the data to only show documents with metrics: `[data_stream][type]: "metrics"` 5. Narrow your search with a known OpenTelemetry field. For example, if you have an `order_value` field, add `order_value: *` to your search to return only OpenTelemetry metrics documents. diff --git a/raw-migrated-files/observability-docs/observability/apm-reduce-apm-storage.md b/raw-migrated-files/observability-docs/observability/apm-reduce-apm-storage.md index 3ed1eafece..978e96cb7b 100644 --- a/raw-migrated-files/observability-docs/observability/apm-reduce-apm-storage.md +++ b/raw-migrated-files/observability-docs/observability/apm-reduce-apm-storage.md @@ -66,7 +66,7 @@ POST /.ds-*-apm*/_delete_by_query {{kib}}'s [Index Management](../../../manage-data/lifecycle/index-lifecycle-management/index-management-in-kibana.md) allows you to manage your cluster’s indices, data streams, index templates, and much more. -To open **Index Management**, find **Stack Management*** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Select ***Data Streams**. Select the data streams you want to delete, and click **Delete data streams**. +To open **Index Management**, find **Stack Management*** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Select ***Data Streams**. Select the data streams you want to delete, and click **Delete data streams**. ## Update existing data [apm-update-data] diff --git a/raw-migrated-files/observability-docs/observability/apm-services.md b/raw-migrated-files/observability-docs/observability/apm-services.md index a04f92b489..e39ce6e8c8 100644 --- a/raw-migrated-files/observability-docs/observability/apm-services.md +++ b/raw-migrated-files/observability-docs/observability/apm-services.md @@ -33,7 +33,7 @@ Group services together to build meaningful views that remove noise, simplify in To create a service group: -1. To open **Service inventory**, find **Applications** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. To open **Service inventory**, find **Applications** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Switch to **Service groups**. 3. Click **Create group**. 4. Specify a name, color, and description. diff --git a/raw-migrated-files/observability-docs/observability/explore-logs.md b/raw-migrated-files/observability-docs/observability/explore-logs.md index 7a71b10054..e280bd35a8 100644 --- a/raw-migrated-files/observability-docs/observability/explore-logs.md +++ b/raw-migrated-files/observability-docs/observability/explore-logs.md @@ -7,7 +7,7 @@ This functionality is in beta and is subject to change. The design and code is l With **Logs Explorer**, you can quickly search and filter your log data, get information about the structure of log fields, and display your findings in a visualization. You can also customize and save your searches and place them on a dashboard. Instead of having to log into different servers, change directories, and view individual files, all your logs are available in a single view. -To open **Logs Explorer**, find `Logs Explorer` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +To open **Logs Explorer**, find `Logs Explorer` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). :::{image} ../../../images/observability-log-explorer.png :alt: Screen capture of the Logs Explorer @@ -22,7 +22,7 @@ Viewing data in Logs Explorer requires `read` privileges for **Discover**, **Ind ## Find your logs [find-your-logs] -By default, Logs Explorer shows all of your logs, according to the index patterns set in the **logs sources** advanced setting. To open **Advanced settings**, find **Stack Management** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +By default, Logs Explorer shows all of your logs, according to the index patterns set in the **logs sources** advanced setting. To open **Advanced settings**, find **Stack Management** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). If you need to focus on logs from a specific integration, select the integration from the logs menu: @@ -68,6 +68,6 @@ The following actions help you filter and focus on specific fields in the log de ## View log data set details [view-log-data-set-details] -Go to **Data Set Quality** to view more details about your data sets and monitor their overall quality. To open **Data Set Quality**, find **Stack Management** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +Go to **Data Set Quality** to view more details about your data sets and monitor their overall quality. To open **Data Set Quality**, find **Stack Management** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Refer to [*Data set quality*](../../../solutions/observability/data-set-quality-monitoring.md) for more information. diff --git a/raw-migrated-files/observability-docs/observability/inspect-metric-anomalies.md b/raw-migrated-files/observability-docs/observability/inspect-metric-anomalies.md index 1f66381b44..7034867ad2 100644 --- a/raw-migrated-files/observability-docs/observability/inspect-metric-anomalies.md +++ b/raw-migrated-files/observability-docs/observability/inspect-metric-anomalies.md @@ -11,7 +11,7 @@ Create a {{ml}} job to detect anomalous memory usage and network traffic automat Once you create {{ml}} jobs, you can not change the settings. You can recreate these jobs later. However, you will remove any previously detected anomalies. -1. To open **Infrastructure inventory**, find **Infrastructure** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. To open **Infrastructure inventory**, find **Infrastructure** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click the **Anomaly detection** link at the top of the page. 3. You’ll be prompted to create a {{ml}} job for **Hosts** or **Kubernetes Pods**. Click **Enable**. 4. Choose a start date for the {{ml}} analysis. diff --git a/raw-migrated-files/observability-docs/observability/logs-ecs-application.md b/raw-migrated-files/observability-docs/observability/logs-ecs-application.md index c24a05a8b3..fede7877ca 100644 --- a/raw-migrated-files/observability-docs/observability/logs-ecs-application.md +++ b/raw-migrated-files/observability-docs/observability/logs-ecs-application.md @@ -260,7 +260,7 @@ Add the custom logs integration to ingest and centrally manage your logs using { To add the custom logs integration to your project: -1. Find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Type `custom` in the search bar and select **Custom Logs**. 3. Click **Install {{agent}}** at the bottom of the page, and follow the instructions for your system to install the {{agent}}. 4. After installing the {{agent}}, click **Save and continue** to configure the integration from the **Add Custom Logs integration** page. diff --git a/raw-migrated-files/observability-docs/observability/logs-filter-and-aggregate.md b/raw-migrated-files/observability-docs/observability/logs-filter-and-aggregate.md index a3f433c5fd..a110f4cb92 100644 --- a/raw-migrated-files/observability-docs/observability/logs-filter-and-aggregate.md +++ b/raw-migrated-files/observability-docs/observability/logs-filter-and-aggregate.md @@ -63,13 +63,13 @@ Filter your data using the fields you’ve extracted so you can focus on log dat ### Filter logs in Logs Explorer [logs-filter-logs-explorer] -Logs Explorer is a {{kib}} tool that automatically provides views of your log data based on integrations and data streams. To open **Logs Explorer**, find `Logs Explorer` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +Logs Explorer is a {{kib}} tool that automatically provides views of your log data based on integrations and data streams. To open **Logs Explorer**, find `Logs Explorer` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). From Logs Explorer, you can use the [{{kib}} Query Language (KQL)](../../../explore-analyze/query-filter/languages/kql.md) in the search bar to narrow down the log data displayed in Logs Explorer. For example, you might want to look into an event that occurred within a specific time range. Add some logs with varying timestamps and log levels to your data stream: -1. To open **Console**, find `Dev Tools` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. To open **Console**, find `Dev Tools` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. In the **Console** tab, run the following command: ```console diff --git a/raw-migrated-files/observability-docs/observability/logs-metrics-get-started.md b/raw-migrated-files/observability-docs/observability/logs-metrics-get-started.md index 0afec03125..84870737b1 100644 --- a/raw-migrated-files/observability-docs/observability/logs-metrics-get-started.md +++ b/raw-migrated-files/observability-docs/observability/logs-metrics-get-started.md @@ -21,7 +21,7 @@ To get started quickly, spin up a deployment of our hosted {{ess}}. The {{ess}} In this step, add the System integration to monitor host logs and metrics. -1. Find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. In the query bar, search for **System** and select the integration to see more details about it. 3. Click **Add System**. 4. Configure the integration name and optionally add a description. Make sure that **Collect logs from System instances** and **Collect metrics from System instances** are turned on. @@ -117,7 +117,7 @@ Next, add additional integrations to the policy used by your agent. Any {{agent}}s assigned to this policy will begin collecting data for the newly configured integrations. -9. To view the data, find **{{fleet}}** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +9. To view the data, find **{{fleet}}** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 10. Click the **Data streams** tab. 11. In the **Actions** column, navigate to the dashboards corresponding to the data stream. diff --git a/raw-migrated-files/observability-docs/observability/logs-parse.md b/raw-migrated-files/observability-docs/observability/logs-parse.md index 0cffc98997..4d0254f3d5 100644 --- a/raw-migrated-files/observability-docs/observability/logs-parse.md +++ b/raw-migrated-files/observability-docs/observability/logs-parse.md @@ -22,7 +22,7 @@ Follow the steps below to see how the following unstructured log data is indexed Start by storing the document in the `logs-example-default` data stream: -1. To open **Console**, find `Dev Tools` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. To open **Console**, find `Dev Tools` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. In the **Console** tab, add the example log to {{es}} using the following command: ```console diff --git a/raw-migrated-files/observability-docs/observability/logs-plaintext.md b/raw-migrated-files/observability-docs/observability/logs-plaintext.md index 60186110e1..5c2296ea43 100644 --- a/raw-migrated-files/observability-docs/observability/logs-plaintext.md +++ b/raw-migrated-files/observability-docs/observability/logs-plaintext.md @@ -272,7 +272,7 @@ Follow these steps to ingest and centrally manage your logs using {{agent}} and To add the custom logs integration to your project: -1. Find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Type `custom` in the search bar and select **Custom Logs**. 3. Click **Add Custom Logs**. 4. Click **Install {{agent}}** at the bottom of the page, and follow the instructions for your system to install the {{agent}}. diff --git a/raw-migrated-files/observability-docs/observability/manage-cases.md b/raw-migrated-files/observability-docs/observability/manage-cases.md index f9b8601d47..e1c04fefae 100644 --- a/raw-migrated-files/observability-docs/observability/manage-cases.md +++ b/raw-migrated-files/observability-docs/observability/manage-cases.md @@ -7,7 +7,7 @@ To perform these tasks, you must have [full access](../../../solutions/observabi Open a new case to keep track of issues and share the details with colleagues. -1. Find **Cases** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Cases** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Create case**. 3. If you defined [templates](../../../solutions/observability/incident-management/configure-case-settings.md#observability-case-templates), optionally select one to use its default field values. [preview] 4. Give the case a name, severity, and description. @@ -63,7 +63,7 @@ To download or delete the file or copy the file hash to your clipboard, open the When you upload a file, a comment is added to the case activity log. To view an image, click its name in the activity or file list. ::::{note} -Uploaded files are also accessible on the **Files** page. To open **Files**, find **Stack Management** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). When you export cases as [saved objects](/explore-analyze/find-and-organize/saved-objects.md), the case files are not exported. +Uploaded files are also accessible on the **Files** page. To open **Files**, find **Stack Management** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). When you export cases as [saved objects](/explore-analyze/find-and-organize/saved-objects.md), the case files are not exported. :::: diff --git a/raw-migrated-files/observability-docs/observability/monitor-datasets.md b/raw-migrated-files/observability-docs/observability/monitor-datasets.md index b83c5c4f52..09f0989182 100644 --- a/raw-migrated-files/observability-docs/observability/monitor-datasets.md +++ b/raw-migrated-files/observability-docs/observability/monitor-datasets.md @@ -4,7 +4,7 @@ The **Data Set Quality** page provides an overview of your log, metric, trace, and synthetic data sets. Use this information to get an idea of your overall data set quality and find data sets that contain incorrectly parsed documents. -To open **Data Set Quality**, find **Stack Management** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). By default, the page only shows log data sets. To see other data set types, select them from the **Type** menu. +To open **Data Set Quality**, find **Stack Management** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). By default, the page only shows log data sets. To see other data set types, select them from the **Type** menu. :::{image} ../../../images/observability-data-set-quality-overview.png :alt: Screen capture of the data set overview diff --git a/raw-migrated-files/observability-docs/observability/monitor-infrastructure-and-hosts.md b/raw-migrated-files/observability-docs/observability/monitor-infrastructure-and-hosts.md index 31eb539785..72724bc955 100644 --- a/raw-migrated-files/observability-docs/observability/monitor-infrastructure-and-hosts.md +++ b/raw-migrated-files/observability-docs/observability/monitor-infrastructure-and-hosts.md @@ -4,7 +4,7 @@ In the {{infrastructure-app}}, visualize infrastructure metrics to help diagnose Using {{agent}} integrations, you can ingest and analyze metrics from servers, Docker containers, Kubernetes orchestrations, explore and analyze application telemetry, and more. -To access the {{infrastructure-app}}, find **Infrastructure** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +To access the {{infrastructure-app}}, find **Infrastructure** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). The {{infrastructure-app}} provides a few different views of your data. diff --git a/raw-migrated-files/observability-docs/observability/obs-ai-assistant.md b/raw-migrated-files/observability-docs/observability/obs-ai-assistant.md index 4cf73f2528..2796747238 100644 --- a/raw-migrated-files/observability-docs/observability/obs-ai-assistant.md +++ b/raw-migrated-files/observability-docs/observability/obs-ai-assistant.md @@ -122,7 +122,7 @@ You can also add information to the knowledge base by asking the AI Assistant to To add external data to the knowledge base in {{kib}}: -1. To open AI Assistant settings, find `AI Assistants` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. To open AI Assistant settings, find `AI Assistants` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Under **Elastic AI Assistant for Observability**, click **Manage settings**. 3. Switch to the **Knowledge base** tab. 4. Click the **New entry** button, and choose either: @@ -157,7 +157,7 @@ By default, the AI Assistant queries all search connector indices. To override t To create a connector in the {{kib}} UI and make its content available to the AI Assistant knowledge base, follow these steps: -1. Open **Connectors** by finding `Content / Connectors` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Open **Connectors** by finding `Content / Connectors` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). ::::{note} If your {{kib}} Space doesn’t include the Search solution you will have to create the connector from a different space or change your space **Solution view** setting to `Classic`. @@ -381,7 +381,7 @@ To learn more about alerting, actions, and connectors, refer to [Alerting](../.. To access the AI Assistant Settings page, you can: -* Find `AI Assistants` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +* Find `AI Assistants` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). * Use the **More actions** menu inside the AI Assistant window. The AI Assistant Settings page contains the following tabs: diff --git a/raw-migrated-files/observability-docs/observability/slo-create.md b/raw-migrated-files/observability-docs/observability/slo-create.md index e3bff32864..2818291a61 100644 --- a/raw-migrated-files/observability-docs/observability/slo-create.md +++ b/raw-migrated-files/observability-docs/observability/slo-create.md @@ -11,7 +11,7 @@ To create and manage SLOs, you need an [appropriate license](https://www.elastic :::: -To create an SLO, find **SLOs** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +To create an SLO, find **SLOs** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). * If you’re creating your first SLO, you’ll see an introductory page. Click the **Create SLO** button. * If you’ve created SLOs before, click the **Create new SLO** button in the upper-right corner of the page. diff --git a/raw-migrated-files/observability-docs/observability/slo-troubleshoot-slos.md b/raw-migrated-files/observability-docs/observability/slo-troubleshoot-slos.md index 4b1f7d4a27..ed9cb9d1b2 100644 --- a/raw-migrated-files/observability-docs/observability/slo-troubleshoot-slos.md +++ b/raw-migrated-files/observability-docs/observability/slo-troubleshoot-slos.md @@ -136,7 +136,7 @@ As mentioned, maintaining a healthy cluster is crucial for SLOs to function corr To be able to inspect SLOs you have to activate the corresponding feature in {{kib}}: -1. Open **Advanced Settings**, by finding **Stack Management** in the main menu or using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Open **Advanced Settings**, by finding **Stack Management** in the main menu or using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Enable `observability:enableInspectEsQueries` setting. Afterwards visit the **SLO edit page** and click **SLO Inspect**. @@ -169,7 +169,7 @@ Before resetting the SLO, verify that the source data and queries are correctly Follow these steps to reset an SLO: -1. Find **SLOs** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **SLOs** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click on the SLO to reset. 3. Select **Actions** → **Reset**. diff --git a/raw-migrated-files/observability-docs/observability/synthetics-analyze.md b/raw-migrated-files/observability-docs/observability/synthetics-analyze.md index 2b5ea07fb9..d62d8dc848 100644 --- a/raw-migrated-files/observability-docs/observability/synthetics-analyze.md +++ b/raw-migrated-files/observability-docs/observability/synthetics-analyze.md @@ -12,7 +12,7 @@ The {{synthetics-app}} in {{kib}} both gives you a high-level overview of your s The Synthetics **Overview** tab provides you with a high-level view of all the services you are monitoring to help you quickly diagnose outages and other connectivity issues within your network. -To access this page, find `Synthetics` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search) and make sure you’re on the **Overview** tab. +To access this page, find `Synthetics` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md) and make sure you’re on the **Overview** tab. This overview includes a snapshot of the current status of all monitors, the number of errors that occurred over the last 6 hours, and the number of alerts over the last 12 hours. All monitors created using projects or using the {{synthetics-app}} will be listed below with information about the location, current status, and duration average. diff --git a/raw-migrated-files/observability-docs/observability/synthetics-configuration.md b/raw-migrated-files/observability-docs/observability/synthetics-configuration.md index 236bc87e0a..4d517a1c74 100644 --- a/raw-migrated-files/observability-docs/observability/synthetics-configuration.md +++ b/raw-migrated-files/observability-docs/observability/synthetics-configuration.md @@ -202,7 +202,7 @@ $$$synthetics-configuration-monitor-tags$$$ `tags` (`Array`) To list available locations you can: * Run the [`elastic-synthetics locations` command](../../../solutions/observability/apps/use-synthetics-cli.md#elastic-synthetics-locations-command). - * Find `Synthetics` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search) and click **Create monitor**. Locations will be listed in *Locations*. + * Find `Synthetics` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md) and click **Create monitor**. Locations will be listed in *Locations*. `privateLocations` (`Array`) @@ -211,7 +211,7 @@ $$$synthetics-configuration-monitor-tags$$$ `tags` (`Array`) To list available {{private-location}}s you can: * Run the [`elastic-synthetics locations` command](../../../solutions/observability/apps/use-synthetics-cli.md#elastic-synthetics-locations-command) with the {{kib}} URL for the deployment from which to fetch available locations. - * Find `Synthetics` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search) and click **Create monitor**. {{private-location}}s will be listed in *Locations*. + * Find `Synthetics` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md) and click **Create monitor**. {{private-location}}s will be listed in *Locations*. `throttling` (`boolean` | [`ThrottlingOptions`](https://github.com/elastic/synthetics/blob/v1.3.0/src/common_types.ts#L194-L198)) diff --git a/raw-migrated-files/observability-docs/observability/synthetics-get-started-project.md b/raw-migrated-files/observability-docs/observability/synthetics-get-started-project.md index 07e0377e48..5689f91c7c 100644 --- a/raw-migrated-files/observability-docs/observability/synthetics-get-started-project.md +++ b/raw-migrated-files/observability-docs/observability/synthetics-get-started-project.md @@ -58,7 +58,7 @@ Then, follow the prompts on screen to setup the correct default variables for yo 1. To generate an API key: - 1. Find `Synthetics` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). + 1. Find `Synthetics` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Settings**. 3. Switch to the **Project API Keys** tab. 4. Click **Generate Project API key**. diff --git a/raw-migrated-files/observability-docs/observability/synthetics-get-started-ui.md b/raw-migrated-files/observability-docs/observability/synthetics-get-started-ui.md index c47309afe1..a0a3d31cde 100644 --- a/raw-migrated-files/observability-docs/observability/synthetics-get-started-ui.md +++ b/raw-migrated-files/observability-docs/observability/synthetics-get-started-ui.md @@ -37,7 +37,7 @@ If you are setting up Synthetics for a deployment configured with [traffic filte To use the {{synthetics-app}} to add a lightweight monitor: -1. Find `Synthetics` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find `Synthetics` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Create monitor**. 3. Set the monitor type to **HTTP Ping**, **TCP Ping**, or **ICMP Ping**. 4. In *Locations*, select one or more locations. diff --git a/raw-migrated-files/observability-docs/observability/synthetics-lightweight.md b/raw-migrated-files/observability-docs/observability/synthetics-lightweight.md index 0a1527e595..8ae8243c42 100644 --- a/raw-migrated-files/observability-docs/observability/synthetics-lightweight.md +++ b/raw-migrated-files/observability-docs/observability/synthetics-lightweight.md @@ -300,7 +300,7 @@ $$$monitor-locations$$$ To list available locations you can: * Run the [`elastic-synthetics locations` command](../../../solutions/observability/apps/use-synthetics-cli.md#elastic-synthetics-locations-command). - * Find `Synthetics` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search) and click **Create monitor**. Locations will be listed in *Locations*. + * Find `Synthetics` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md) and click **Create monitor**. Locations will be listed in *Locations*. **Examples**: @@ -332,7 +332,7 @@ $$$monitor-private_locations$$$ To list available {{private-location}}s you can: * Run the [`elastic-synthetics locations` command](../../../solutions/observability/apps/use-synthetics-cli.md#elastic-synthetics-locations-command) and specify the {{kib}} URL of the deployment. This will fetch all available private locations associated with the deployment. - * Find `Synthetics` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search) and click **Create monitor**. {{private-location}}s will be listed in *Locations*. + * Find `Synthetics` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md) and click **Create monitor**. {{private-location}}s will be listed in *Locations*. **Examples**: diff --git a/raw-migrated-files/observability-docs/observability/synthetics-private-location.md b/raw-migrated-files/observability-docs/observability/synthetics-private-location.md index cf7c0f75dc..a329cc93b1 100644 --- a/raw-migrated-files/observability-docs/observability/synthetics-private-location.md +++ b/raw-migrated-files/observability-docs/observability/synthetics-private-location.md @@ -84,7 +84,7 @@ You may need to set other environment variables. Learn how in [{{agent}} environ When the {{agent}} is running you can add a new {{private-location}} in {{kib}}: -1. Find `Synthetics` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find `Synthetics` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Settings**. 3. Click **{{private-location}}s**. 4. Click **Add location**. diff --git a/raw-migrated-files/observability-docs/observability/triage-threshold-breaches.md b/raw-migrated-files/observability-docs/observability/triage-threshold-breaches.md index f97003f286..a84f62648d 100644 --- a/raw-migrated-files/observability-docs/observability/triage-threshold-breaches.md +++ b/raw-migrated-files/observability-docs/observability/triage-threshold-breaches.md @@ -9,7 +9,7 @@ Threshold breaches occur when an {{observability}} data type reaches or exceeds To triage issues quickly, go to the alert details page: -1. Find **Alerts** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Alerts** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. From the Alerts table, click the ![More actions](../../../images/observability-boxesHorizontal.svg "") icon next to the alert and select **View alert details**. The alert details page shows information about the alert, including when the alert was triggered, the duration of the alert, and the last status update. If there is a "group by" field specified in the rule, the page also includes the source. You can follow the links to navigate to the rule definition. diff --git a/raw-migrated-files/observability-docs/observability/view-infrastructure-metrics.md b/raw-migrated-files/observability-docs/observability/view-infrastructure-metrics.md index a3c122e21d..58356bde39 100644 --- a/raw-migrated-files/observability-docs/observability/view-infrastructure-metrics.md +++ b/raw-migrated-files/observability-docs/observability/view-infrastructure-metrics.md @@ -2,7 +2,7 @@ The **Infrastructure inventory** page provides a metrics-driven view of your entire infrastructure grouped by the resources you are monitoring. All monitored resources emitting a core set of infrastructure metrics are displayed to give you a quick view of the overall health of your infrastructure. -To open **Infrastructure inventory**, find **Infrastructure** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +To open **Infrastructure inventory**, find **Infrastructure** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). :::{image} ../../../images/observability-metrics-app.png :alt: Infrastructure inventory diff --git a/raw-migrated-files/security-docs/security/add-exceptions.md b/raw-migrated-files/security-docs/security/add-exceptions.md index 6de6e6e16b..7a152ef4a8 100644 --- a/raw-migrated-files/security-docs/security/add-exceptions.md +++ b/raw-migrated-files/security-docs/security/add-exceptions.md @@ -28,7 +28,7 @@ You can add exceptions to a rule from the rule details page, the Alerts table, t * To add an exception from the rule details page: - 1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). + 1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. In the Rules table, search for the rule that you want to add an exception to, then click its name to open the rule details. 3. Scroll down the rule details page, select the **Rule exceptions** tab, then click **Add rule exception**. @@ -39,18 +39,18 @@ You can add exceptions to a rule from the rule details page, the Alerts table, t * To add an exception from the Alerts table: - 1. Find **Alerts** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). + 1. Find **Alerts** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Scroll down to the Alerts table, go to the alert you want to create an exception for, click the **More Actions** menu (**…​**), then select **Add rule exception**. * To add an exception from the alert details flyout: - 1. Find **Alerts** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). + 1. Find **Alerts** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click the **View details** button from the Alerts table. 3. In the alert details flyout, click **Take action → Add rule exception**. * To add an exception from the Shared Exception Lists page: - 1. Find the **Shared exception lists** page in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). + 1. Find the **Shared exception lists** page in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Create shared exception list** → **Create exception item**. 2. In the **Add rule exception** flyout, name the exception. @@ -159,18 +159,18 @@ Additionally, to add an Endpoint exception to an endpoint protection rule, there * To add an Endpoint exception from the rule details page: - 1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). + 1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. In the Rules table, search for and select one of the [endpoint protection rules](../../../solutions/security/manage-elastic-defend/endpoint-protection-rules.md). 3. Scroll down the rule details page, select the **Endpoint exceptions** tab, then click **Add endpoint exception**. * To add an Endpoint exception from the Alerts table: - 1. Find **Alerts** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). + 1. Find **Alerts** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Scroll down to the Alerts table, and from an {{elastic-endpoint}} alert, click the **More actions** menu (**…​**), then select **Add Endpoint exception**. * To add an Endpoint exception from Shared Exception Lists page: - 1. Find the **Shared exception lists** page in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). + 1. Find the **Shared exception lists** page in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Expand the Endpoint Security Exception List or click the list name to open the list’s details page. Next, click **Add endpoint exception**. ::::{note} @@ -271,7 +271,7 @@ Creates an exception that excludes all LFC-signed trusted processes: To view a rule’s exceptions: -1. Open the rule’s details page. To do this, find **Detection rules (SIEM)** in the navigation menu or look for “Detection rules (SIEM)” using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), search for the rule that you want to examine, then click the rule’s name to open its details. +1. Open the rule’s details page. To do this, find **Detection rules (SIEM)** in the navigation menu or look for “Detection rules (SIEM)” using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), search for the rule that you want to examine, then click the rule’s name to open its details. 2. Scroll down and select the **Rule exceptions** or **Endpoint exceptions** tab. All exceptions that belong to the rule will display in a list. From the list, you can filter, edit, and delete exceptions. You can also toggle between **Active exceptions** and **Expired exceptions**. diff --git a/raw-migrated-files/security-docs/security/add-manage-notes.md b/raw-migrated-files/security-docs/security/add-manage-notes.md index 3a3cffde64..61cb20c0c0 100644 --- a/raw-migrated-files/security-docs/security/add-manage-notes.md +++ b/raw-migrated-files/security-docs/security/add-manage-notes.md @@ -39,7 +39,7 @@ After notes are created, the **Notes** Timeline tab displays the total number of ## Manage all notes [manage-notes] -Use the **Notes** page to view and interact with all existing notes. To access the page, navigate to **Investigations** in the main navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), then go to **Notes**. From the **Notes** page, you can: +Use the **Notes** page to view and interact with all existing notes. To access the page, navigate to **Investigations** in the main navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then go to **Notes**. From the **Notes** page, you can: * Search for specific notes * Filter notes by the user who created them or by the object they’re attached to (notes can be attached to alerts, events, or Timelines) diff --git a/raw-migrated-files/security-docs/security/agent-tamper-protection.md b/raw-migrated-files/security-docs/security/agent-tamper-protection.md index 7a5f346c3d..e836ff19da 100644 --- a/raw-migrated-files/security-docs/security/agent-tamper-protection.md +++ b/raw-migrated-files/security-docs/security/agent-tamper-protection.md @@ -23,7 +23,7 @@ When enabled, {{agent}} and {{elastic-endpoint}} can only be uninstalled on the You can enable Agent tamper protection by configuring the {{agent}} policy. -1. Find **{{fleet}}** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **{{fleet}}** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Select **Agent policies**, then select the Agent policy you want to configure. 3. Select the **Settings** tab on the policy details page. 4. In the **Agent tamper protection** section, turn on the **Prevent agent tampering** setting. diff --git a/raw-migrated-files/security-docs/security/ai-assistant-knowledge-base.md b/raw-migrated-files/security-docs/security/ai-assistant-knowledge-base.md index 2cbf644147..88f595fdd9 100644 --- a/raw-migrated-files/security-docs/security/ai-assistant-knowledge-base.md +++ b/raw-migrated-files/security-docs/security/ai-assistant-knowledge-base.md @@ -51,7 +51,7 @@ Knowledge base setup may take several minutes. It will continue in the backgroun ### Option 2: Enable Knowledge Base from the Security AI settings [_option_2_enable_knowledge_base_from_the_security_ai_settings] -1. To open **Security AI settings**, use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search) to find "AI Assistant for Security." +1. To open **Security AI settings**, use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md) to find "AI Assistant for Security." 2. On the **Knowledge Base** tab, click **Setup Knowledge Base**. If the button doesn’t appear, Knowledge Base is already enabled. :::{image} ../../../images/security-knowledge-base-assistant-settings-kb-tab.png @@ -88,7 +88,7 @@ When you enable Knowledge Base, it comes pre-populated with articles from [Elast Add an individual document to Knowledge Base when you want AI Assistant to remember a specific piece of information. -1. To open **Security AI settings**, use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search) to find "AI Assistant for Security." Select the **Knowledge Base** tab. +1. To open **Security AI settings**, use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md) to find "AI Assistant for Security." Select the **Knowledge Base** tab. 2. Click **New → Document** and give it a name. 3. Under **Sharing**, select whether this knowledge should be **Global** or **Private**. 4. Write the knowledge AI Assistant should remember in the **Markdown text** field. @@ -121,7 +121,7 @@ Indices added to Knowledge Base must have at least one field mapped as [semantic :::: -1. To open **Security AI settings**, use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search) to find "AI Assistant for Security." Select the **Knowledge Base** tab. +1. To open **Security AI settings**, use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md) to find "AI Assistant for Security." Select the **Knowledge Base** tab. 2. Click **New → Index**. 3. Name the knowledge source. 4. Under **Sharing**, select whether this knowledge should be **Global** or **Private**. @@ -163,7 +163,7 @@ This section provides an example of adding a threat intelligence feed to Knowled First, you’ll need to set up a web crawler to add the desired data to an index, then you’ll need to add that index to Knowledge Base. -1. From the **Search** section of {{kib}}, find **Web crawlers** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. From the **Search** section of {{kib}}, find **Web crawlers** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **New web crawler**. 1. Under **Index name**, name the index where the data from your new web crawler will be stored, for example `threat_intelligence_feed_1`. Click **Create index**. diff --git a/raw-migrated-files/security-docs/security/artifact-control.md b/raw-migrated-files/security-docs/security/artifact-control.md index aca5ecb555..1250d02c75 100644 --- a/raw-migrated-files/security-docs/security/artifact-control.md +++ b/raw-migrated-files/security-docs/security/artifact-control.md @@ -13,7 +13,7 @@ It is strongly advised to keep automatic updates enabled to ensure the highest l To configure the protection artifacts version deployed in your environment: -1. Find **Policies** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Policies** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Select an {{elastic-defend}} integration policy, then select the **Protection updates** tab. 3. Turn off the **Enable automatic updates** toggle. 4. Use the **Version to deploy** date picker to select the date of the protection artifacts you want to use in your environment. diff --git a/raw-migrated-files/security-docs/security/asset-criticality.md b/raw-migrated-files/security-docs/security/asset-criticality.md index 3c7e3704ba..e9d2d446b4 100644 --- a/raw-migrated-files/security-docs/security/asset-criticality.md +++ b/raw-migrated-files/security-docs/security/asset-criticality.md @@ -89,7 +89,7 @@ host,host-001,extreme_impact To import a file: -1. Find **Entity Store** in the main menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Entity Store** in the main menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Select or drag and drop the file you want to import. ::::{note} diff --git a/raw-migrated-files/security-docs/security/assistant-connect-to-azure-openai.md b/raw-migrated-files/security-docs/security/assistant-connect-to-azure-openai.md index 6aa03a4452..6c4df9a369 100644 --- a/raw-migrated-files/security-docs/security/assistant-connect-to-azure-openai.md +++ b/raw-migrated-files/security-docs/security/assistant-connect-to-azure-openai.md @@ -99,7 +99,7 @@ The following video demonstrates these steps. Finally, configure the connector in {{kib}}: 1. Log in to {{kib}}. -2. Find the **Connectors** page in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Then click **Create Connector**, and select **OpenAI**. +2. Find the **Connectors** page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Then click **Create Connector**, and select **OpenAI**. 3. Give your connector a name to help you keep track of different models, such as `Azure OpenAI (GPT-4 Turbo v. 0125)`. 4. For **Select an OpenAI provider**, choose **Azure OpenAI**. 5. Update the **URL** field. We recommend doing the following: diff --git a/raw-migrated-files/security-docs/security/assistant-connect-to-bedrock.md b/raw-migrated-files/security-docs/security/assistant-connect-to-bedrock.md index f3317a62f5..04ffead451 100644 --- a/raw-migrated-files/security-docs/security/assistant-connect-to-bedrock.md +++ b/raw-migrated-files/security-docs/security/assistant-connect-to-bedrock.md @@ -146,7 +146,7 @@ The following video demonstrates these steps. Finally, configure the connector in {{kib}}: 1. Log in to {{kib}}. -2. . Find the **Connectors** page in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Then click **Create Connector**, and select **Amazon Bedrock**. +2. . Find the **Connectors** page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Then click **Create Connector**, and select **Amazon Bedrock**. 3. Name your connector. 4. (Optional) Configure the Amazon Bedrock connector to use a different AWS region where Anthropic models are supported by editing the **URL** field, for example by changing `us-east-1` to `eu-central-1`. 5. (Optional) Add one of the following strings if you want to use a model other than the default: diff --git a/raw-migrated-files/security-docs/security/assistant-connect-to-openai.md b/raw-migrated-files/security-docs/security/assistant-connect-to-openai.md index 58f04c0342..2620594dc1 100644 --- a/raw-migrated-files/security-docs/security/assistant-connect-to-openai.md +++ b/raw-migrated-files/security-docs/security/assistant-connect-to-openai.md @@ -47,7 +47,7 @@ The following video demonstrates these steps. To integrate with {{kib}}: 1. Log in to {{kib}}. -2. Find the **Connectors** page in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Then click **Create Connector**, and select **OpenAI**. +2. Find the **Connectors** page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Then click **Create Connector**, and select **OpenAI**. 3. Provide a name for your connector, such as `OpenAI (GPT-4 Turbo Preview)`, to help keep track of the model and version you are using. 4. Under **Select an OpenAI provider**, choose **OpenAI**. 5. The **URL** field can be left as default. diff --git a/raw-migrated-files/security-docs/security/benchmark-rules.md b/raw-migrated-files/security-docs/security/benchmark-rules.md index 69155d7c9d..f8ab6a0572 100644 --- a/raw-migrated-files/security-docs/security/benchmark-rules.md +++ b/raw-migrated-files/security-docs/security/benchmark-rules.md @@ -29,7 +29,7 @@ Benchmark rules are not editable. ## Review your benchmarks [_review_your_benchmarks_2] -Find **Benchmarks** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). From there, you can click a benchmark’s name to view the benchmark rules associated with it. You can click a benchmark rule’s name to see details including information about how to remediate it, and related links. +Find **Benchmarks** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). From there, you can click a benchmark’s name to view the benchmark rules associated with it. You can click a benchmark rule’s name to see details including information about how to remediate it, and related links. Benchmark rules are enabled by default, but you can disable some of them — at the benchmark level — to suit your environment. This means for example that if you have two integrations using the `CIS AWS` benchmark, disabling a rule for that benchmark affects both integrations. To enable or disable a rule, use the **Enabled** toggle on the right of the rules table. diff --git a/raw-migrated-files/security-docs/security/blocklist.md b/raw-migrated-files/security-docs/security/blocklist.md index 9c7157fe98..786b2c0423 100644 --- a/raw-migrated-files/security-docs/security/blocklist.md +++ b/raw-migrated-files/security-docs/security/blocklist.md @@ -13,7 +13,7 @@ The blocklist is not intended to broadly block benign applications for non-secur By default, a blocklist entry is recognized globally across all hosts running {{elastic-defend}}. If you have a [Platinum or Enterprise subscription](https://www.elastic.co/pricing), you can also assign a blocklist entry to specific {{elastic-defend}} integration policies, which blocks the process only on hosts assigned to that policy. -1. Find **Blocklist** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Blocklist** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Add blocklist entry**. The **Add blocklist** flyout appears. 3. Fill in these fields in the **Details** section: diff --git a/raw-migrated-files/security-docs/security/building-block-rule.md b/raw-migrated-files/security-docs/security/building-block-rule.md index 1c1e4cc839..504288d839 100644 --- a/raw-migrated-files/security-docs/security/building-block-rule.md +++ b/raw-migrated-files/security-docs/security/building-block-rule.md @@ -20,7 +20,7 @@ To create a rule that searches alert indices, select **Index Patterns** as the r By default, building block alerts are excluded from the Overview and Alerts pages. You can choose to include building block alerts on the Alerts page, which expands the number of alerts. -1. Find **Alerts** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Alerts** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. In the Alerts table, select **Additional filters** → **Include building block alerts**, located on the far-right. ::::{note} diff --git a/raw-migrated-files/security-docs/security/cases-manage-settings.md b/raw-migrated-files/security-docs/security/cases-manage-settings.md index 3a04f6702b..59a6b63ab5 100644 --- a/raw-migrated-files/security-docs/security/cases-manage-settings.md +++ b/raw-migrated-files/security-docs/security/cases-manage-settings.md @@ -1,6 +1,6 @@ # Configure case settings [cases-manage-settings] -To change case closure options, add custom fields, templates, and connectors for external incident management systems, and create custom observable types, find **Cases** in the navigation menu or search for `Security/Cases` by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), then click **Settings**. +To change case closure options, add custom fields, templates, and connectors for external incident management systems, and create custom observable types, find **Cases** in the navigation menu or search for `Security/Cases` by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then click **Settings**. :::{image} ../../../images/security-cases-settings.png :alt: Shows the case settings page diff --git a/raw-migrated-files/security-docs/security/cases-open-manage.md b/raw-migrated-files/security-docs/security/cases-open-manage.md index 522c01a018..5aea620440 100644 --- a/raw-migrated-files/security-docs/security/cases-open-manage.md +++ b/raw-migrated-files/security-docs/security/cases-open-manage.md @@ -7,7 +7,7 @@ You can create and manage cases using the UI or the [cases API](https://www.elas Open a new case to keep track of security issues and share their details with colleagues. -1. Find **Cases** in the navigation menu or search for `Security/Cases` by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), then click **Create case**. If no cases exist, the Cases table will be empty and you’ll be prompted to create one by clicking the **Create case** button inside the table. +1. Find **Cases** in the navigation menu or search for `Security/Cases` by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then click **Create case**. If no cases exist, the Cases table will be empty and you’ll be prompted to create one by clicking the **Create case** button inside the table. 2. If you defined [templates](../../../solutions/security/investigate/configure-case-settings.md#cases-templates), you can optionally select one to use its default field values. [preview] 3. Give the case a name, assign a severity level, and provide a description. You can use [Markdown](https://www.markdownguide.org/cheat-sheet) syntax in the case description. @@ -272,7 +272,7 @@ The following attachments are *not* exported: To export a case: -1. Find **Saved Objects** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Saved Objects** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Search for the case by choosing a saved object type or entering the case title in the search bar. 3. Select one or more cases, then click the **Export** button. 4. Click **Export**. A confirmation message that your file is downloading displays. @@ -292,7 +292,7 @@ To export a case: To import a case: -1. Find **Saved Objects** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Saved Objects** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Import**. 3. Select the NDJSON file containing the exported case and configure the import options. 4. Click **Import**. diff --git a/raw-migrated-files/security-docs/security/conf-map-ui.md b/raw-migrated-files/security-docs/security/conf-map-ui.md index 2c23b94f4f..45d487541b 100644 --- a/raw-migrated-files/security-docs/security/conf-map-ui.md +++ b/raw-migrated-files/security-docs/security/conf-map-ui.md @@ -19,7 +19,7 @@ To view the map, you need a role with at least `Read` [privileges](../../../depl ## Create {{kib}} data views [kibana-index-pattern] -To display map data, you must define a {{kib}} [data view](../../../explore-analyze/find-and-organize/data-views.md) that includes one or more of the indices specified in the `securitysolution:defaultIndex` field. To view those indices, find **Stack Management** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), then go to **Advanced Settings** → **`securitysolution:defaultIndex`**. +To display map data, you must define a {{kib}} [data view](../../../explore-analyze/find-and-organize/data-views.md) that includes one or more of the indices specified in the `securitysolution:defaultIndex` field. To view those indices, find **Stack Management** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then go to **Advanced Settings** → **`securitysolution:defaultIndex`**. For example, to display data that is stored in indices matching the index pattern `servers-europe-*` on the map, you must use a {{kib}} data view whose index pattern matches `servers-europe-*`, such as `servers-*`. diff --git a/raw-migrated-files/security-docs/security/configure-endpoint-integration-policy.md b/raw-migrated-files/security-docs/security/configure-endpoint-integration-policy.md index 862a29a1f1..6674df299d 100644 --- a/raw-migrated-files/security-docs/security/configure-endpoint-integration-policy.md +++ b/raw-migrated-files/security-docs/security/configure-endpoint-integration-policy.md @@ -2,7 +2,7 @@ After the {{agent}} is installed with the {{elastic-defend}} integration, several protections features — including preventions against malware, ransomware, memory threats, and malicious behavior — are automatically enabled on protected hosts (some features require a Platinum or Enterprise license). If needed, you can update the integration policy to configure protection settings, event collection, antivirus settings, trusted applications, event filters, host isolation exceptions, and blocked applications to meet your organization’s security needs. -You can also create multiple {{elastic-defend}} integration policies to maintain unique configuration profiles. To create an additional {{elastic-defend}} integration policy, find **Integrations** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), then follow the steps for [adding the {{elastic-defend}} integration](../../../solutions/security/configure-elastic-defend/install-elastic-defend.md#add-security-integration). +You can also create multiple {{elastic-defend}} integration policies to maintain unique configuration profiles. To create an additional {{elastic-defend}} integration policy, find **Integrations** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then follow the steps for [adding the {{elastic-defend}} integration](../../../solutions/security/configure-elastic-defend/install-elastic-defend.md#add-security-integration). ::::{admonition} Requirements You must have the **{{elastic-defend}} Policy Management : All** [privilege](../../../solutions/security/configure-elastic-defend/elastic-defend-feature-privileges.md) to configure an integration policy. @@ -17,7 +17,7 @@ In addition to configuring an {{elastic-defend}} policy through the {{elastic-se To configure an integration policy: -1. Find **Policies** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Policies** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Select the integration policy you want to configure. The integration policy configuration page appears. 3. On the **Policy settings** tab, review and configure the following settings as appropriate: @@ -39,7 +39,7 @@ To configure an integration policy: * Assign an existing artifact (Platinum or Enterprise subscription) — Click **Assign *x* to policy**, then select an item from the flyout. This view lists any existing artifacts that aren’t already assigned to the current policy. ::::{note} - You can’t create a new endpoint policy artifact while configuring an integration policy. To create a new artifact, go to its main page in the {{security-app}} (for example, to create a new trusted application, find **Trusted applications** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search)). + You can’t create a new endpoint policy artifact while configuring an integration policy. To create a new artifact, go to its main page in the {{security-app}} (for example, to create a new trusted application, find **Trusted applications** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md)). :::: 5. Click the **Protection updates** tab to configure how {{elastic-defend}} receives updates from Elastic with the latest threat detections, malware models, and other protection artifacts. Refer to [Configure updates for protection artifacts](../../../solutions/security/configure-elastic-defend/configure-updates-for-protection-artifacts.md) for more information. diff --git a/raw-migrated-files/security-docs/security/connect-to-byo-llm.md b/raw-migrated-files/security-docs/security/connect-to-byo-llm.md index 6672648660..0399990c73 100644 --- a/raw-migrated-files/security-docs/security/connect-to-byo-llm.md +++ b/raw-migrated-files/security-docs/security/connect-to-byo-llm.md @@ -194,7 +194,7 @@ You can monitor the performance of the host running LM Studio using Elastic’s Finally, configure the connector: 1. Log in to your Elastic deployment. -2. Find the **Connectors** page in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Then click **Create Connector**, and select **OpenAI**. The OpenAI connector enables this use case because LM Studio uses the OpenAI SDK. +2. Find the **Connectors** page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Then click **Create Connector**, and select **OpenAI**. The OpenAI connector enables this use case because LM Studio uses the OpenAI SDK. 3. Name your connector to help keep track of the model version you are using. 4. Under **Select an OpenAI provider**, select **Other (OpenAI Compatible Service)**. 5. Under **URL**, enter the domain name specified in your Nginx configuration file, followed by `/v1/chat/completions`. diff --git a/raw-migrated-files/security-docs/security/connect-to-vertex.md b/raw-migrated-files/security-docs/security/connect-to-vertex.md index dad4821253..e25dbf6984 100644 --- a/raw-migrated-files/security-docs/security/connect-to-vertex.md +++ b/raw-migrated-files/security-docs/security/connect-to-vertex.md @@ -90,7 +90,7 @@ The following video demonstrates these steps. Finally, configure the connector in your Elastic deployment: 1. Log in to your Elastic deployment. -2. Find the **Connectors** page in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Then click **Create Connector**, select **Google Gemini**. +2. Find the **Connectors** page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Then click **Create Connector**, select **Google Gemini**. 3. Name your connector to help keep track of the model version you are using. 4. Under **URL**, enter the URL for your region. 5. Enter your **GCP Region** and **GCP Project ID**. diff --git a/raw-migrated-files/security-docs/security/cspm-benchmark-rules.md b/raw-migrated-files/security-docs/security/cspm-benchmark-rules.md index c6343d8662..c638c28711 100644 --- a/raw-migrated-files/security-docs/security/cspm-benchmark-rules.md +++ b/raw-migrated-files/security-docs/security/cspm-benchmark-rules.md @@ -29,7 +29,7 @@ Benchmark rules are not editable. ## Review your benchmarks [_review_your_benchmarks] -Find **Benchmarks** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). From there, you can click a benchmark’s name to view the benchmark rules associated with it. You can click a benchmark rule’s name to see details including information about how to remediate it, and related links. +Find **Benchmarks** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). From there, you can click a benchmark’s name to view the benchmark rules associated with it. You can click a benchmark rule’s name to see details including information about how to remediate it, and related links. Benchmark rules are enabled by default, but you can disable some of them — at the benchmark level — to suit your environment. This means for example that if you have two integrations using the `CIS AWS` benchmark, disabling a rule for that benchmark affects both integrations. To enable or disable a rule, use the **Enabled** toggle on the right of the rules table. diff --git a/raw-migrated-files/security-docs/security/cspm-get-started-azure.md b/raw-migrated-files/security-docs/security/cspm-get-started-azure.md index 5a4a4c445c..3a14d0e65c 100644 --- a/raw-migrated-files/security-docs/security/cspm-get-started-azure.md +++ b/raw-migrated-files/security-docs/security/cspm-get-started-azure.md @@ -28,7 +28,7 @@ This functionality is in beta and is subject to change. The design and code is l :::: -1. Find **Integrations** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Integrations** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Search for `CSPM`, then click on the result. 3. Click **Add Cloud Security Posture Management (CSPM)**. 4. Select **Azure**, then either **Azure Organization** to onboard your whole organization, or **Single Subscription** to onboard an individual subscription. @@ -43,7 +43,7 @@ This functionality is in beta and is subject to change. The design and code is l ### Add your CSPM integration [cspm-add-and-name-integration-azure] -1. Find **Integrations** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Integrations** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Search for `CSPM`, then click on the result. 3. Click **Add Cloud Security Posture Management (CSPM)**. 4. Under **Configure integration**, select **Azure***, then select either ***Azure Organization** or **Single Subscription**, depending on which resources you want to monitor. diff --git a/raw-migrated-files/security-docs/security/cspm-get-started-gcp.md b/raw-migrated-files/security-docs/security/cspm-get-started-gcp.md index 8eb84b11b9..6395d4487f 100644 --- a/raw-migrated-files/security-docs/security/cspm-get-started-gcp.md +++ b/raw-migrated-files/security-docs/security/cspm-get-started-gcp.md @@ -28,7 +28,7 @@ This functionality is in beta and is subject to change. The design and code is l :::: -1. Find **Integrations** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Integrations** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Search for `CSPM`, then click on the result. 3. Click **Add Cloud Security Posture Management (CSPM)**. 4. Select **GCP**, then either **GCP Organization** to onboard your whole organization, or **Single Account** to onboard an individual account. @@ -43,7 +43,7 @@ This functionality is in beta and is subject to change. The design and code is l ### Add your CSPM integration [cspm-add-and-name-integration-gcp] -1. Find **Integrations** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Integrations** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Search for `CSPM`, then click on the result. 3. Click **Add Cloud Security Posture Management (CSPM)**. 4. Under **Configure integration**, select **GCP**, then either **GCP Organization** (recommended) or **Single Account**. diff --git a/raw-migrated-files/security-docs/security/cspm-get-started.md b/raw-migrated-files/security-docs/security/cspm-get-started.md index 2bcf413662..9ecae81038 100644 --- a/raw-migrated-files/security-docs/security/cspm-get-started.md +++ b/raw-migrated-files/security-docs/security/cspm-get-started.md @@ -28,7 +28,7 @@ This functionality is in beta and is subject to change. The design and code is l :::: -1. Find **Integrations** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Integrations** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Search for `CSPM`, then click on the result. 3. Click **Add Cloud Security Posture Management (CSPM)**. 4. Select **AWS**, then either **AWS Organization** to onboard multiple accounts, or **Single Account** to onboard an individual account. @@ -52,7 +52,7 @@ This functionality is in beta and is subject to change. The design and code is l ### Add the CSPM integration [cspm-add-and-name-integration] -1. Find **Integrations** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Integrations** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Search for `CSPM`, then click on the result. 3. Click **Add Cloud Security Posture Management (CSPM)**. 4. Select **AWS**, then either **AWS Organization** to onboard multiple accounts, or **Single Account** to onboard an individual account. diff --git a/raw-migrated-files/security-docs/security/endpoint-diagnostic-data.md b/raw-migrated-files/security-docs/security/endpoint-diagnostic-data.md index a08cab6a3e..6245c9baf8 100644 --- a/raw-migrated-files/security-docs/security/endpoint-diagnostic-data.md +++ b/raw-migrated-files/security-docs/security/endpoint-diagnostic-data.md @@ -7,7 +7,7 @@ By default, {{elastic-defend}} streams diagnostic data to your cluster, which El :::: -1. To view the Endpoints list, find **Endpoints** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. To view the Endpoints list, find **Endpoints** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Locate the endpoint for which you want to disable diagnostic data, then click the integration policy in the **Policy** column. 3. Scroll down to the bottom of the policy and click **Show advanced settings**. 4. Enter `false` for these settings: diff --git a/raw-migrated-files/security-docs/security/endpoint-management-req.md b/raw-migrated-files/security-docs/security/endpoint-management-req.md index 029d292d26..a7eaff2097 100644 --- a/raw-migrated-files/security-docs/security/endpoint-management-req.md +++ b/raw-migrated-files/security-docs/security/endpoint-management-req.md @@ -2,7 +2,7 @@ You can create user roles and define privileges to manage feature access in {{elastic-sec}}. This allows you to use the principle of least privilege while managing access to {{elastic-defend}}'s features. -To configure roles and privileges, find **Roles** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). For more details on using this UI, refer to [{{kib}} privileges](../../../deploy-manage/users-roles/cluster-or-deployment-auth/defining-roles.md#adding_kibana_privileges). +To configure roles and privileges, find **Roles** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). For more details on using this UI, refer to [{{kib}} privileges](../../../deploy-manage/users-roles/cluster-or-deployment-auth/defining-roles.md#adding_kibana_privileges). ::::{note} {{elastic-defend}}'s feature privileges must be assigned to **All Spaces**. You can’t assign them to an individual space. diff --git a/raw-migrated-files/security-docs/security/environment-variable-capture.md b/raw-migrated-files/security-docs/security/environment-variable-capture.md index d2514be48c..7f71bc0e66 100644 --- a/raw-migrated-files/security-docs/security/environment-variable-capture.md +++ b/raw-migrated-files/security-docs/security/environment-variable-capture.md @@ -18,7 +18,7 @@ You can configure an {{agent}} policy to capture up to five environment variable To set up environment variable capture for an {{agent}} policy: -1. Find **Policies** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Policies** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Select an {{agent}} policy. 3. Click **Show advanced settings**. 4. Scroll down or search for `linux.advanced.capture_env_vars` or `mac.advanced.capture_env_vars`. diff --git a/raw-migrated-files/security-docs/security/get-started-with-kspm.md b/raw-migrated-files/security-docs/security/get-started-with-kspm.md index f658616efc..0d549aeff5 100644 --- a/raw-migrated-files/security-docs/security/get-started-with-kspm.md +++ b/raw-migrated-files/security-docs/security/get-started-with-kspm.md @@ -37,7 +37,7 @@ The instructions differ depending on whether you’re installing on EKS or on un ### Name your integration and select a Kubernetes Deployment type [_name_your_integration_and_select_a_kubernetes_deployment_type] -1. Find **Cloud Security Posture** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Cloud Security Posture** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Add a KSPM integration**. 3. Read the integration’s description to understand how it works. Then, click [**Add Kubernetes Security Posture Management**](https://docs.elastic.co/en/integrations/cloud_security_posture). 4. Name your integration. Use a name that matches the purpose or team of the cluster(s) you want to monitor, for example, `IT-dev-k8s-clusters`. @@ -235,7 +235,7 @@ Follow these steps to deploy the KSPM integration to unmanaged clusters. Keep in To install the integration on unmanaged clusters: -1. Find **Cloud Security Posture** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Cloud Security Posture** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Add a KSPM integration**. 3. Read the integration’s description to understand how it works. Then, click [**Add Kubernetes Security Posture Management**](https://docs.elastic.co/en/integrations/cloud_security_posture). 4. Name your integration. Use a name that matches the purpose or team of the cluster(s) you want to monitor, for example, `IT-dev-k8s-clusters`. diff --git a/raw-migrated-files/security-docs/security/host-isolation-exceptions.md b/raw-migrated-files/security-docs/security/host-isolation-exceptions.md index 8315da5fcd..94bd1c2ce9 100644 --- a/raw-migrated-files/security-docs/security/host-isolation-exceptions.md +++ b/raw-migrated-files/security-docs/security/host-isolation-exceptions.md @@ -19,7 +19,7 @@ You must have the **Host Isolation Exceptions** [privilege](../../../solutions/s Host isolation is a [Platinum or Enterprise subscription](https://www.elastic.co/pricing) feature. By default, a host isolation exception is recognized globally across all hosts running {{elastic-defend}}. You can also assign a host isolation exception to a specific {{elastic-defend}} integration policy, affecting only the hosts assigned to that policy. -1. Find **Host isolation exceptions** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Host isolation exceptions** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Add Host isolation exception**. 3. Fill in these fields in the **Add Host isolation exception** flyout: diff --git a/raw-migrated-files/security-docs/security/host-isolation-ov.md b/raw-migrated-files/security-docs/security/host-isolation-ov.md index dc60dfb98d..379b61e501 100644 --- a/raw-migrated-files/security-docs/security/host-isolation-ov.md +++ b/raw-migrated-files/security-docs/security/host-isolation-ov.md @@ -50,7 +50,7 @@ All actions executed on a host are tracked in the host’s response actions hist ::::{dropdown} Isolate a host from an endpoint -1. Find **Endpoints** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), then either: +1. Find **Endpoints** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then either: * Select the appropriate endpoint in the **Endpoint** column, and click **Take action → Isolate host** in the endpoint details flyout. * Click the **Actions** menu (**…​**) on the appropriate endpoint, then select **Isolate host**. @@ -124,7 +124,7 @@ After the host is successfully isolated, an **Isolated** status is added to the ::::{dropdown} Release a host from an endpoint -1. Find **Endpoints** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), then either: +1. Find **Endpoints** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then either: * Select the appropriate endpoint in the **Endpoint** column, and click **Take action → Release host** in the endpoint details flyout. * Click the **Actions** menu (**…​**) on the appropriate endpoint, then select **Release host**. diff --git a/raw-migrated-files/security-docs/security/ingest-falco.md b/raw-migrated-files/security-docs/security/ingest-falco.md index 8ebfe53202..58169c8fd2 100644 --- a/raw-migrated-files/security-docs/security/ingest-falco.md +++ b/raw-migrated-files/security-docs/security/ingest-falco.md @@ -18,7 +18,7 @@ In {{elastic-sec}}: Next, to make alerts from Falco appear on {{elastic-sec}}'s Alerts page: -1. Find the **Rules** page in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find the **Rules** page in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Detection rules (SIEM)**. 3. Search for a rule called `External Alerts`. Install it if necessary, and enable it. diff --git a/raw-migrated-files/security-docs/security/install-endpoint.md b/raw-migrated-files/security-docs/security/install-endpoint.md index 02198f22eb..ddf9ac9a96 100644 --- a/raw-migrated-files/security-docs/security/install-endpoint.md +++ b/raw-migrated-files/security-docs/security/install-endpoint.md @@ -28,7 +28,7 @@ If you’re using macOS, some versions may require you to grant Full Disk Access ## Add the {{elastic-defend}} integration [add-security-integration] -1. Find **Integrations** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Integrations** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). :::{image} ../../../images/security-endpoint-cloud-sec-integrations-page.png :alt: Search result for "{{elastic-defend}}" on the Integrations page. @@ -90,7 +90,7 @@ If you have upgraded to an {{stack}} version that includes {{fleet-server}} 7.13 ### Add the {{agent}} [enroll-agent] -1. If you’re in the process of installing an {{agent}} integration (such as {{elastic-defend}}), the **Add agent** UI opens automatically. Otherwise, find **{{fleet}}*** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), and select ***Agents** → **Add agent**. +1. If you’re in the process of installing an {{agent}} integration (such as {{elastic-defend}}), the **Add agent** UI opens automatically. Otherwise, find **{{fleet}}*** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), and select ***Agents** → **Add agent**. :::{image} ../../../images/security-endpoint-cloud-sec-add-agent.png :alt: Add agent flyout on the Fleet page. diff --git a/raw-migrated-files/security-docs/security/invest-guide-run-osquery.md b/raw-migrated-files/security-docs/security/invest-guide-run-osquery.md index 2f4ecf94ca..35601a3f3c 100644 --- a/raw-migrated-files/security-docs/security/invest-guide-run-osquery.md +++ b/raw-migrated-files/security-docs/security/invest-guide-run-osquery.md @@ -23,7 +23,7 @@ You can only add Osquery to investigation guides for custom rules because prebui :::: -1. Go to the **Rules** page. To access it, find **Detection rules (SIEM)** in the main menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Go to the **Rules** page. To access it, find **Detection rules (SIEM)** in the main menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Select a rule to open the its details, then click **Edit rule settings**. 3. Select the **About** tab, then expand the rule’s advanced settings. 4. Scroll down to the Investigation guide section. In the toolbar, click the **Osquery** button (![Click the Osquery button](../../../images/security-osquery-button.png "")). @@ -52,7 +52,7 @@ You can only add Osquery to investigation guides for custom rules because prebui ## Run live queries from an investigation guide [run-live-queries-ig] -1. Go to the **Rules** page. To access it, find **Detection rules (SIEM)** in the main menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Go to the **Rules** page. To access it, find **Detection rules (SIEM)** in the main menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Select a rule to open the its details. 3. Go to **Rules** → **Detection rules (SIEM)**, then select a rule to open its details. 4. Go to the About section of the rule details page and click **Investigation guide**. diff --git a/raw-migrated-files/security-docs/security/linux-file-monitoring.md b/raw-migrated-files/security-docs/security/linux-file-monitoring.md index 4e165cc512..98e0fd97fa 100644 --- a/raw-migrated-files/security-docs/security/linux-file-monitoring.md +++ b/raw-migrated-files/security-docs/security/linux-file-monitoring.md @@ -7,7 +7,7 @@ Ignoring file systems can create gaps in your security coverage. Use additional :::: -To monitor or ignore additional file systems, configure the following advanced settings related to **fanotify**, a Linux feature that monitors file system events. Find **Policies** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), click a policy’s name, then scroll down and select **Show advanced settings**. +To monitor or ignore additional file systems, configure the following advanced settings related to **fanotify**, a Linux feature that monitors file system events. Find **Policies** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), click a policy’s name, then scroll down and select **Show advanced settings**. ::::{note} Even when configured to monitor all file systems (`ignore_unknown_filesystems` is `false`), {{elastic-defend}} will still ignore specific file systems that Elastic has internally identified as incompatible. The following settings apply to any *other* file systems. @@ -58,7 +58,7 @@ In a typical setup, when you install {{agent}}, {{filebeat}} is installed alongs To find the system file name: -1. Find **Hosts** in the navigation menu, or search for `Security/Explore/Hosts` by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Hosts** in the navigation menu, or search for `Security/Explore/Hosts` by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. From the Hosts page, search for `message: "Current sync path"` to reveal the file path. 3. If you have access to the endpoint, run `findmnt -o FSTYPE -T ` to return the file system. For example: diff --git a/raw-migrated-files/security-docs/security/machine-learning.md b/raw-migrated-files/security-docs/security/machine-learning.md index 4282b8ad2f..5f5dc63415 100644 --- a/raw-migrated-files/security-docs/security/machine-learning.md +++ b/raw-migrated-files/security-docs/security/machine-learning.md @@ -39,7 +39,7 @@ You can also check the status of {{ml}} detection rules, and start or stop their {{elastic-sec}} comes with prebuilt {{ml}} {anomaly-jobs} for automatically detecting host and network anomalies. The jobs are displayed in the `Anomaly Detection` interface. They are available when either: -* You ship data using [Beats](https://www.elastic.co/products/beats) or the [{{agent}}](../../../solutions/security/configure-elastic-defend/install-elastic-defend.md), and {{kib}} is configured with the required index patterns (such as `auditbeat-*`, `filebeat-*`, `packetbeat-*`, or `winlogbeat-*`) on the **Data Views** page. To find this page, navigate to **Data Views** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +* You ship data using [Beats](https://www.elastic.co/products/beats) or the [{{agent}}](../../../solutions/security/configure-elastic-defend/install-elastic-defend.md), and {{kib}} is configured with the required index patterns (such as `auditbeat-*`, `filebeat-*`, `packetbeat-*`, or `winlogbeat-*`) on the **Data Views** page. To find this page, navigate to **Data Views** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Or diff --git a/raw-migrated-files/security-docs/security/prebuilt-rules-management.md b/raw-migrated-files/security-docs/security/prebuilt-rules-management.md index 9ff1672ff1..986c285213 100644 --- a/raw-migrated-files/security-docs/security/prebuilt-rules-management.md +++ b/raw-migrated-files/security-docs/security/prebuilt-rules-management.md @@ -19,7 +19,7 @@ Follow these guidelines to start using the {{security-app}}'s [prebuilt rules](h ## Install and enable Elastic prebuilt rules [load-prebuilt-rules] -1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), then go to the Rules table. +1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then go to the Rules table. The badge next to **Add Elastic rules** shows the number of prebuilt rules available for installation. @@ -86,7 +86,7 @@ Each prebuilt rule includes several tags identifying the rule’s purpose, detec ## Select and duplicate all prebuilt rules [select-all-prebuilt-rules] -1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. In the **Rules** table, select the **Elastic rules** filter. 3. Click **Select all *x* rules** above the rules table. 4. Click **Bulk actions** → **Duplicate**. @@ -99,7 +99,7 @@ You can then modify the duplicated rules and, if required, delete the prebuilt o Elastic regularly updates prebuilt rules to optimize their performance and ensure they detect the latest threats and techniques. When updated versions are available for your installed prebuilt rules, the **Rule Updates** tab appears on the **Rules** page, allowing you to update your installed rules with the latest versions. -1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. In the **Rules** table, select the **Rule Updates** tab. ::::{note} diff --git a/raw-migrated-files/security-docs/security/response-actions-config.md b/raw-migrated-files/security-docs/security/response-actions-config.md index bcba889adb..0814ea386f 100644 --- a/raw-migrated-files/security-docs/security/response-actions-config.md +++ b/raw-migrated-files/security-docs/security/response-actions-config.md @@ -36,7 +36,7 @@ Expand a section below for your endpoint security system: 2. **Install the CrowdStrike integration and {{agent}}.** Elastic’s [CrowdStrike integration](https://docs.elastic.co/en/integrations/crowdstrike) collects and ingests logs into {{elastic-sec}}. - 1. Find **Integrations** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), search for and select **CrowdStrike**, then select **Add CrowdStrike**. + 1. Find **Integrations** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), search for and select **CrowdStrike**, then select **Add CrowdStrike**. 2. Configure the integration with an **Integration name** and optional **Description**. 3. Select **Collect CrowdStrike logs via API**, and enter the required **Settings**: @@ -56,7 +56,7 @@ Expand a section below for your endpoint security system: :::: - 1. Find **Connectors** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), then select **Create connector**. + 1. Find **Connectors** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then select **Create connector**. 2. Select the CrowdStrike connector. 3. Enter the configuration information: @@ -92,7 +92,7 @@ Expand a section below for your endpoint security system: :::: - 1. Find **Integrations** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), search for and select **Microsoft Defender for Endpoint**, then select **Add Microsoft Defender for Endpoint**. + 1. Find **Integrations** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), search for and select **Microsoft Defender for Endpoint**, then select **Add Microsoft Defender for Endpoint**. 2. Enter an **Integration name**. Entering a **Description** is optional. 3. Ensure that **Microsoft Defender for Endpoint logs** is selected, and enter the required values for **Client ID***, ***Client Secret**, and **Tenant ID**. 4. Scroll down and enter a name for the agent policy in **New agent policy name**. If other agent policies already exist, you can click the **Existing hosts** tab and select an existing policy instead. For more details on {{agent}} configuration settings, refer to [{{agent}} policies](https://www.elastic.co/guide/en/fleet/current/agent-policy.html). @@ -106,7 +106,7 @@ Expand a section below for your endpoint security system: :::: - 1. Find **Connectors** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), then select **Create connector**. + 1. Find **Connectors** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then select **Create connector**. 2. Select the Microsoft Defender for Endpoint connector. 3. Enter the configuration information: @@ -146,7 +146,7 @@ Expand a section below for your endpoint security system: 2. **Install the SentinelOne integration and {{agent}}.** Elastic’s [SentinelOne integration](https://docs.elastic.co/en/integrations/sentinel_one) collects and ingests logs into {{elastic-sec}}. - 1. Find **Integrations** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), search for and select **SentinelOne**, then select **Add SentinelOne**. + 1. Find **Integrations** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), search for and select **SentinelOne**, then select **Add SentinelOne**. 2. Configure the integration with an **Integration name** and optional **Description**. 3. Ensure that **Collect SentinelOne logs via API** is selected, and enter the required **Settings**: @@ -164,7 +164,7 @@ Expand a section below for your endpoint security system: :::: - 1. Find **Connectors** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), then select **Create connector**. + 1. Find **Connectors** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then select **Create connector**. 2. Select the **SentinelOne** connector. 3. Enter the configuration information: diff --git a/raw-migrated-files/security-docs/security/response-actions-history.md b/raw-migrated-files/security-docs/security/response-actions-history.md index 24aded20a5..1ea5e14e90 100644 --- a/raw-migrated-files/security-docs/security/response-actions-history.md +++ b/raw-migrated-files/security-docs/security/response-actions-history.md @@ -8,7 +8,7 @@ You must have the **Response Actions History** [privilege](../../../solutions/se :::: -To access the response actions history for all endpoints, find **Response actions history** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). You can also access the response actions history for an individual endpoint from these areas: +To access the response actions history for all endpoints, find **Response actions history** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). You can also access the response actions history for an individual endpoint from these areas: * **Endpoints** page: Click an endpoint’s name to open the details flyout, then click the **Response actions history** tab. * **Response console** page: Click the **Response actions history** button. diff --git a/raw-migrated-files/security-docs/security/rules-coverage.md b/raw-migrated-files/security-docs/security/rules-coverage.md index 447ddb3976..0e1cf57e1b 100644 --- a/raw-migrated-files/security-docs/security/rules-coverage.md +++ b/raw-migrated-files/security-docs/security/rules-coverage.md @@ -4,7 +4,7 @@ The **MITRE ATT&CK® coverage** page shows which [MITRE ATT&CK®](https://attack Mirroring the MITRE ATT&CK® framework, columns represent major tactics, and cells within each column represent a tactic’s related techniques. Cells are darker when a technique has more rules matching the current filters, as indicated in the **Legend** at the top. -To access the **MITRE ATT&CK® coverage** page, find **Detection rules (SIEM)** in the navigation menu or look for “Detection rules (SIEM)” using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), then go to **MITRE ATT&CK® coverage**. +To access the **MITRE ATT&CK® coverage** page, find **Detection rules (SIEM)** in the navigation menu or look for “Detection rules (SIEM)” using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then go to **MITRE ATT&CK® coverage**. ::::{note} This page only includes the detection rules you currently have installed, and only rules that are mapped to MITRE ATT&CK®. The coverage page maps detections to the following [MITRE ATT&CK® version](https://attack.mitre.org/resources/updates/updates-april-2024) used by {{elastic-sec}}: `v15.1`. Elastic prebuilt rules that aren’t installed and custom rules that are either unmapped or mapped to a deprecated tactic or technique will not appear on the coverage map. diff --git a/raw-migrated-files/security-docs/security/rules-ui-create.md b/raw-migrated-files/security-docs/security/rules-ui-create.md index afe52626c3..3f600dbeb9 100644 --- a/raw-migrated-files/security-docs/security/rules-ui-create.md +++ b/raw-migrated-files/security-docs/security/rules-ui-create.md @@ -37,7 +37,7 @@ To create or edit {{ml}} rules, you must have the [appropriate license](https:// :::: -1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Create new rule**. 3. To create a rule based on a {{ml}} anomaly threshold, select **Machine Learning** on the **Create new rule** page, then select: @@ -65,7 +65,7 @@ To create or edit {{ml}} rules, you must have the [appropriate license](https:// ## Create a custom query rule [create-custom-rule] -1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Create new rule**. 3. To create a rule based on a KQL or Lucene query, select **Custom query** on the **Create new rule** page, then: @@ -110,7 +110,7 @@ To create or edit {{ml}} rules, you must have the [appropriate license](https:// ## Create a threshold rule [create-threshold-rule] -1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Create new rule**. 3. To create a rule based on a source event field threshold, select **Threshold** on the **Create new rule** page, then: @@ -153,7 +153,7 @@ To create or edit {{ml}} rules, you must have the [appropriate license](https:// ## Create an event correlation rule [create-eql-rule] -1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Create new rule**. 3. To create an event correlation rule using EQL, select **Event Correlation** on the **Create new rule** page, then: 4. To create an event correlation rule using EQL, select **Event Correlation**, then: @@ -223,7 +223,7 @@ To create or edit {{ml}} rules, you must have the [appropriate license](https:// :::: -1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Create new rule**. 3. To create a rule that searches for events whose specified field value matches the specified indicator field value in the indicator index patterns, select **Indicator Match** on the **Create new rule** page, then fill in the following fields: @@ -316,7 +316,7 @@ You uploaded a value list of known ransomware domains, and you want to be notifi ## Create a new terms rule [create-new-terms-rule] -1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Create new rule**. 3. To create a rule that searches for each new term detected in source documents, select **New Terms** on the **Create new rule** page, then: @@ -357,7 +357,7 @@ Use [{{esql}}](../../../explore-analyze/query-filter/languages/esql.md) to query To create an {{esql}} rule: -1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Create new rule**. 3. Select **{{esql}}**, then write a query. diff --git a/raw-migrated-files/security-docs/security/rules-ui-management.md b/raw-migrated-files/security-docs/security/rules-ui-management.md index 11d1d2d665..fecac9e4ab 100644 --- a/raw-migrated-files/security-docs/security/rules-ui-management.md +++ b/raw-migrated-files/security-docs/security/rules-ui-management.md @@ -63,7 +63,7 @@ Similarly, rules will be skipped if they can’t be modified by a bulk edit. For :::: -1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Do one of the following: * Edit a single rule: Select the **All actions** menu (**…​**) on a rule, then select **Edit rule settings**. The **Edit rule settings** view opens, where you can modify the [rule’s settings](../../../solutions/security/detect-and-alert/create-detection-rule.md). @@ -106,7 +106,7 @@ When duplicating a rule with exceptions, you can choose to duplicate the rule an :::: -1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. In the Rules table, do one of the following: * Select the **All actions** menu (**…​**) on a rule, then select an action. @@ -130,7 +130,7 @@ Before manually running rules, make sure you properly understand and plan for ru :::: -1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. In the **Rules** table, do one of the following: * Select the **All actions** menu (**…​**) on a rule, then select **Manual run**. @@ -199,7 +199,7 @@ The `.ndjson` file also includes any actions, connectors, and exception lists re To export and import detection rules: -1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. To export rules: 1. In the Rules table, select the rules you want to export. diff --git a/raw-migrated-files/security-docs/security/security-posture-management.md b/raw-migrated-files/security-docs/security/security-posture-management.md index d9debe4dd7..79c655398e 100644 --- a/raw-migrated-files/security-docs/security/security-posture-management.md +++ b/raw-migrated-files/security-docs/security/security-posture-management.md @@ -22,14 +22,14 @@ Using the data generated by these features, you can: **Identify and secure misconfigured infrastructure:** -1. Find **Cloud Security Posture** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Cloud Security Posture** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **View all failed findings**, either for an individual resource or a group of resources. 3. Click a failed finding to open the Findings flyout. 4. Follow the steps under Remediation to fix the misconfiguration. **Identify the CIS Sections (security best practice categories) with which your resources are least compliant:** -1. Find **Cloud Security Posture** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Cloud Security Posture** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Do one of the following: 1. Under Failed findings by CIS section, click the name of a CIS section to view all failed findings from that section. diff --git a/raw-migrated-files/security-docs/security/self-healing-rollback.md b/raw-migrated-files/security-docs/security/self-healing-rollback.md index be3c1536df..ed24420312 100644 --- a/raw-migrated-files/security-docs/security/self-healing-rollback.md +++ b/raw-migrated-files/security-docs/security/self-healing-rollback.md @@ -14,7 +14,7 @@ Also, rollback is triggered by *every* {{elastic-defend}} prevention alert, so y :::: -1. Find **Policies** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), then select the integration policy you want to configure. +1. Find **Policies** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then select the integration policy you want to configure. 2. Scroll down to the bottom of the policy and click **Show advanced settings**. 3. Enter `true` for the setting `windows.advanced.alerts.rollback.self_healing.enabled`. 4. Click **Save**. diff --git a/raw-migrated-files/security-docs/security/session-view.md b/raw-migrated-files/security-docs/security/session-view.md index b6bca14ff6..c6f8d18e7a 100644 --- a/raw-migrated-files/security-docs/security/session-view.md +++ b/raw-migrated-files/security-docs/security/session-view.md @@ -27,7 +27,7 @@ To view Linux session data from your Kubernetes infrastructure, you’ll need to Session View uses process data collected by the {{elastic-defend}} integration, but this data is not always collected by default. To confirm that Session View data is enabled: -1. Find **Policies** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Policies** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Select one or more of your {{elastic-defend}} integration policies to edit. 3. Select the **Policy settings** tab, then scroll down to the Linux event collection section near the bottom. 4. Check the box for **Process** events, and turn on the **Collect session data** toggle. @@ -109,7 +109,7 @@ From a security perspective, terminal output is important because it offers a me To enable terminal output data capture: -1. Find **Policies** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Policies** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Select one or more of your {{elastic-defend}} integration policies to edit. 3. On the **Policy settings** tab, scroll down to the Linux event collection section near the bottom of the page and select the **Collect session data** and **Capture terminal output** options. diff --git a/raw-migrated-files/security-docs/security/shared-exception-lists.md b/raw-migrated-files/security-docs/security/shared-exception-lists.md index 0e539f8f97..ff651f4306 100644 --- a/raw-migrated-files/security-docs/security/shared-exception-lists.md +++ b/raw-migrated-files/security-docs/security/shared-exception-lists.md @@ -17,7 +17,7 @@ Exception lists created in 8.5 and earlier become shared exception lists in 8.6 Set up shared exception lists to contain exception items: -1. Find the **Shared exception lists** page in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find the **Shared exception lists** page in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Create shared exception list** → **Create shared list**. 3. Give the shared exception list a name. 4. (Optional) Provide a description. @@ -28,7 +28,7 @@ Set up shared exception lists to contain exception items: Add exception items: -1. Find the **Shared exception lists** page in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find the **Shared exception lists** page in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Create shared exception list** → **Create exception item**. ::::{tip} @@ -78,7 +78,7 @@ Add exception items: Apply shared exception lists to rules: -1. Find the **Shared exception lists** page in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find the **Shared exception lists** page in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Do one of the following: * Select a shared exception list’s name to open its details page, then click **Link rules**. diff --git a/raw-migrated-files/security-docs/security/timeline-templates-ui.md b/raw-migrated-files/security-docs/security/timeline-templates-ui.md index 2372dcb3bc..63212b5fe3 100644 --- a/raw-migrated-files/security-docs/security/timeline-templates-ui.md +++ b/raw-migrated-files/security-docs/security/timeline-templates-ui.md @@ -67,7 +67,7 @@ To enable the filter, either specify a value or change it to a field’s existin 1. Choose one of the following: - * Find **Timelines** in the main menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Next, select the **Templates** tab, then click **Create new Timeline template**. + * Find **Timelines** in the main menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Next, select the **Templates** tab, then click **Create new Timeline template**. * Go to the Timeline bar (which is at the bottom of most pages), click the ![Click the add new button](../../../images/security-add-new-timeline-button.png "") button, then click **Create new Timeline template**. * From an open Timeline or Timeline template, click **New** → **New Timeline template**. @@ -106,7 +106,7 @@ When alerts generated by rules associated with this template are investigated in You can view, duplicate, export, delete, and create templates from existing Timelines: -1. Find **Timelines** in the main menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), then select the **Templates** tab. +1. Find **Timelines** in the main menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then select the **Templates** tab. :::{image} ../../../images/security-all-actions-timeline-ui.png :alt: all actions timeline ui @@ -138,7 +138,7 @@ You cannot delete prebuilt templates. You can import and export Timeline templates, which enables importing templates from one space or {{elastic-sec}} instance to another. Exported templates are saved in an `ndjson` file. -1. Find **Timelines** in the main menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), then select the **Templates** tab. +1. Find **Timelines** in the main menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then select the **Templates** tab. 2. To export templates, do one of the following: * To export one template, click the **All actions** icon in the relevant row and then select **Export selected**. diff --git a/raw-migrated-files/security-docs/security/timelines-ui.md b/raw-migrated-files/security-docs/security/timelines-ui.md index 45ce6e4da0..9f60c67913 100644 --- a/raw-migrated-files/security-docs/security/timelines-ui.md +++ b/raw-migrated-files/security-docs/security/timelines-ui.md @@ -16,7 +16,7 @@ In addition to Timelines, you can create and attach Timeline templates to [detec To make a new Timeline, choose one of the following: -* Find **Timelines** in the main menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), then click **Create new Timeline**. +* Find **Timelines** in the main menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then click **Create new Timeline**. * Go to the Timeline bar (which is at the bottom of most pages), click the ![Click the add new button](../../../images/security-add-new-timeline-button.png "") button, then click **Create new Timeline template**. * From an open Timeline or Timeline template, click **New** → **New Timeline**. @@ -179,7 +179,7 @@ You can export and import Timelines, which enables you to share Timelines from o To export Timelines: -* Find **Timelines** in the main menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +* Find **Timelines** in the main menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). * Either click the **All actions** menu in the relevant row and select **Export selected**, or select multiple Timelines and then click **Bulk actions** → **Export selected**. To import Timelines: diff --git a/raw-migrated-files/security-docs/security/trusted-apps-ov.md b/raw-migrated-files/security-docs/security/trusted-apps-ov.md index 921263c163..082dde3e35 100644 --- a/raw-migrated-files/security-docs/security/trusted-apps-ov.md +++ b/raw-migrated-files/security-docs/security/trusted-apps-ov.md @@ -23,7 +23,7 @@ By default, a trusted application is recognized globally across all hosts runnin To add a trusted application: -1. Find **Trusted applications** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Trusted applications** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Add trusted application**. 3. Fill in the following fields in the **Add trusted application** flyout: diff --git a/raw-migrated-files/security-docs/security/tuning-anomaly-results.md b/raw-migrated-files/security-docs/security/tuning-anomaly-results.md index aabd334b60..b621de0b68 100644 --- a/raw-migrated-files/security-docs/security/tuning-anomaly-results.md +++ b/raw-migrated-files/security-docs/security/tuning-anomaly-results.md @@ -19,7 +19,7 @@ For example, to filter out results from a housekeeping process, named `maintenan ### Create a filter list [create-fiter-list] -1. Find **Machine Learning** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Machine Learning** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Under **Anomaly Detection**, select **Settings**. 3. Click **Filter Lists** and then **New**. diff --git a/raw-migrated-files/security-docs/security/tuning-detection-signals.md b/raw-migrated-files/security-docs/security/tuning-detection-signals.md index 12e0247e28..7d30c9eae7 100644 --- a/raw-migrated-files/security-docs/security/tuning-detection-signals.md +++ b/raw-migrated-files/security-docs/security/tuning-detection-signals.md @@ -27,7 +27,7 @@ Organizations frequently use uncommon and in-house applications. Occasionally, t For example, to prevent the [Unusual Process Execution Path - Alternate Data Stream](https://www.elastic.co/guide/en/security/current/unusual-process-execution-path-alternate-data-stream.html) rule from producing alerts for an in-house application named `myautomatedbuild`: -1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. In the Rules table, search for and then click on the **Unusual Process Execution Path - Alternate Data Stream** rule. The **Unusual Process Execution Path - Alternate Data Stream** rule details page is displayed. diff --git a/raw-migrated-files/security-docs/security/turn-on-risk-engine.md b/raw-migrated-files/security-docs/security/turn-on-risk-engine.md index 94d58217c1..ad9aa274f5 100644 --- a/raw-migrated-files/security-docs/security/turn-on-risk-engine.md +++ b/raw-migrated-files/security-docs/security/turn-on-risk-engine.md @@ -15,7 +15,7 @@ The preview is limited to two risk scores per {{kib}} instance. :::: -To preview risky entities, find **Entity Risk Score** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +To preview risky entities, find **Entity Risk Score** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). :::{image} ../../../images/security-preview-risky-entities.png :alt: Preview of risky entities diff --git a/raw-migrated-files/security-docs/security/uninstall-agent.md b/raw-migrated-files/security-docs/security/uninstall-agent.md index b737a85958..a96226a926 100644 --- a/raw-migrated-files/security-docs/security/uninstall-agent.md +++ b/raw-migrated-files/security-docs/security/uninstall-agent.md @@ -2,7 +2,7 @@ To uninstall {{agent}} from a host, run the `uninstall` command from the directory where it’s running. Refer to the [{{fleet}} and {{agent}} documentation](https://www.elastic.co/guide/en/fleet/current/uninstall-elastic-agent.html) for more information. -If [Agent tamper protection](../../../solutions/security/configure-elastic-defend/prevent-elastic-agent-uninstallation.md) is enabled on the Agent policy for the host, you’ll need to include the uninstall token in the command, using the `--uninstall-token` flag. You can [find the uninstall token](../../../solutions/security/configure-elastic-defend/prevent-elastic-agent-uninstallation.md#fleet-uninstall-tokens) on the Agent policy. Alternatively, find **{{fleet}}** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), and select **Uninstall tokens**. +If [Agent tamper protection](../../../solutions/security/configure-elastic-defend/prevent-elastic-agent-uninstallation.md) is enabled on the Agent policy for the host, you’ll need to include the uninstall token in the command, using the `--uninstall-token` flag. You can [find the uninstall token](../../../solutions/security/configure-elastic-defend/prevent-elastic-agent-uninstallation.md#fleet-uninstall-tokens) on the Agent policy. Alternatively, find **{{fleet}}** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), and select **Uninstall tokens**. For example, to uninstall {{agent}} on a macOS or Linux host: diff --git a/raw-migrated-files/security-docs/security/value-lists-exceptions.md b/raw-migrated-files/security-docs/security/value-lists-exceptions.md index db8872da98..27ef3616cf 100644 --- a/raw-migrated-files/security-docs/security/value-lists-exceptions.md +++ b/raw-migrated-files/security-docs/security/value-lists-exceptions.md @@ -37,7 +37,7 @@ To create a value list: :::: -2. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +2. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 3. Click **Manage value lists**. The **Manage value lists** window opens. :::{image} ../../../images/security-upload-lists-ui.png @@ -62,7 +62,7 @@ You can edit, remove, or export existing value lists. ### Edit value lists [edit-value-lists] -1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Manage value lists**. The **Manage value lists** window opens. 3. In the **Value lists** table, click the value list you want to edit. 4. Do any of the following: @@ -90,7 +90,7 @@ You can also edit value lists while creating and managing exceptions that use va ### Export or remove value lists [export-remove-value-lists] -1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Detection rules (SIEM)** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Manage value lists**. The **Manage value lists** window opens. 3. From the **Value lists** table, you can: diff --git a/raw-migrated-files/security-docs/security/visual-event-analyzer.md b/raw-migrated-files/security-docs/security/visual-event-analyzer.md index 1ed6c13534..b826da28ea 100644 --- a/raw-migrated-files/security-docs/security/visual-event-analyzer.md +++ b/raw-migrated-files/security-docs/security/visual-event-analyzer.md @@ -21,8 +21,8 @@ To find events that can be visually analyzed: 1. First, display a list of events by doing one of the following: - * Find **Hosts** in the main menu, or search for `Security/Explore/Hosts` by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), then select the **Events** tab. A list of all your hosts' events appears at the bottom of the page. - * Find **Alerts** in the main menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), then scroll down to the Alerts table. + * Find **Hosts** in the main menu, or search for `Security/Explore/Hosts` by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then select the **Events** tab. A list of all your hosts' events appears at the bottom of the page. + * Find **Alerts** in the main menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then scroll down to the Alerts table. 2. Filter events that can be visually analyzed by entering either of the following queries in the KQL search bar, then selecting **Enter**: diff --git a/raw-migrated-files/security-docs/security/vuln-management-get-started.md b/raw-migrated-files/security-docs/security/vuln-management-get-started.md index a7a276f7fe..95c42caeb9 100644 --- a/raw-migrated-files/security-docs/security/vuln-management-get-started.md +++ b/raw-migrated-files/security-docs/security/vuln-management-get-started.md @@ -35,7 +35,7 @@ Do not add the integration to an existing {{agent}} policy. It should always be ### Step 1: Add the CNVM integration [vuln-management-setup-step-1] -1. Find **Integrations** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Integrations** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Search for **Cloud Native Vulnerability Management**, then click on the result. 3. Click **Add Cloud Native Vulnerability Management**. 4. Give your integration a name that matches its purpose or the AWS account region you want to scan for vulnerabilities (for example, `uswest2-aws-account`.) diff --git a/raw-migrated-files/toc.yml b/raw-migrated-files/toc.yml index 496760b637..df39317fcc 100644 --- a/raw-migrated-files/toc.yml +++ b/raw-migrated-files/toc.yml @@ -641,10 +641,8 @@ toc: - file: kibana/kibana/data-rollups.md - file: kibana/kibana/elasticsearch-mutual-tls.md - file: kibana/kibana/esql.md - - file: kibana/kibana/get-started.md - file: kibana/kibana/install.md - file: kibana/kibana/kibana-authentication.md - - file: kibana/kibana/kibana-concepts-analysts.md - file: kibana/kibana/kibana-role-management.md - file: kibana/kibana/logging-settings.md - file: kibana/kibana/management.md diff --git a/solutions/observability/apps/api-keys.md b/solutions/observability/apps/api-keys.md index ac0739c32c..4f96d6247b 100644 --- a/solutions/observability/apps/api-keys.md +++ b/solutions/observability/apps/api-keys.md @@ -92,7 +92,7 @@ Assign the newly created `apm_agent_key_role` role to any user that wishes to cr The Applications UI has a built-in workflow that you can use to easily create and view {{apm-agent}} API keys. Only API keys created in the Applications UI will show up here. -Using a superuser account, or a user with the role created in the previous step, In {{kib}}, find **Applications** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Go to **Settings** → **Agent keys**. Enter a name for your API key and select at least one privilege. +Using a superuser account, or a user with the role created in the previous step, In {{kib}}, find **Applications** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Go to **Settings** → **Agent keys**. Enter a name for your API key and select at least one privilege. For example, to create an API key that can be used to ingest APM events and read agent central configuration, select `config_agent:read` and `event:write`. diff --git a/solutions/observability/apps/apm-agent-authorization.md b/solutions/observability/apps/apm-agent-authorization.md index e219e94b94..1f232522e9 100644 --- a/solutions/observability/apps/apm-agent-authorization.md +++ b/solutions/observability/apps/apm-agent-authorization.md @@ -37,7 +37,7 @@ max_procs: 4 ::::::{tab-item} Fleet-managed Configure and customize Fleet-managed APM settings directly in {{kib}}: -1. In {{kib}}, find **Fleet** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. In {{kib}}, find **Fleet** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Under the **Agent policies** tab, select the policy you would like to configure. 3. Find the Elastic APM integration and select **Actions** > **Edit integration**. 4. Look for these settings under **Agent authorization**. diff --git a/solutions/observability/apps/configure-anonymous-authentication.md b/solutions/observability/apps/configure-anonymous-authentication.md index d1cf2330f5..ee77561338 100644 --- a/solutions/observability/apps/configure-anonymous-authentication.md +++ b/solutions/observability/apps/configure-anonymous-authentication.md @@ -38,7 +38,7 @@ apm-server.auth.anonymous.rate_limit.ip_limit: 1000 ::::::{tab-item} Fleet-managed Configure and customize Fleet-managed APM settings directly in {{kib}}: -1. In {{kib}}, find **Fleet** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. In {{kib}}, find **Fleet** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Under the **Agent policies** tab, select the policy you would like to configure. 3. Find the Elastic APM integration and select **Actions** > **Edit integration**. 4. Look for these settings under **Agent authorization**. diff --git a/solutions/observability/apps/configure-real-user-monitoring-rum.md b/solutions/observability/apps/configure-real-user-monitoring-rum.md index 448884b558..f189b8199b 100644 --- a/solutions/observability/apps/configure-real-user-monitoring-rum.md +++ b/solutions/observability/apps/configure-real-user-monitoring-rum.md @@ -46,7 +46,7 @@ To enable RUM, set [Enable RUM](#apm-rum-enable) to `true`. Configure and customize Fleet-managed APM settings directly in {{kib}}: -1. In {{kib}}, find **Fleet** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. In {{kib}}, find **Fleet** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Under the **Agent policies** tab, select the policy you would like to configure. 3. Find the Elastic APM integration and select **Actions** > **Edit integration**. 4. Look for these options under **Real User Monitoring**. diff --git a/solutions/observability/apps/control-access-to-apm-data.md b/solutions/observability/apps/control-access-to-apm-data.md index 536e18bb7a..2673ee43f8 100644 --- a/solutions/observability/apps/control-access-to-apm-data.md +++ b/solutions/observability/apps/control-access-to-apm-data.md @@ -234,7 +234,7 @@ POST /_aliases?pretty ### Step 2: Create {{kib}} spaces [_step_2_create_kib_spaces] -Next, you’ll need to create a {{kib}} space for each service environment. To open **Spaces**, find **Stack Management** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). To create a new space, click **Create a space**. For this guide, we’ve created two Kibana spaces, one named `production` and one named `staging`. +Next, you’ll need to create a {{kib}} space for each service environment. To open **Spaces**, find **Stack Management** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). To create a new space, click **Create a space**. For this guide, we’ve created two Kibana spaces, one named `production` and one named `staging`. See [Kibana spaces](../../../deploy-manage/manage-spaces.md) for more information on creating a space. @@ -255,7 +255,7 @@ Open the Applications UI and navigate to **Settings** → **Indices**. Use the t ### Step 4: Create {{kib}} access roles [_step_4_create_kib_access_roles] -To open **Roles**, find **Stack Management** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Click **Create role**. +To open **Roles**, find **Stack Management** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Click **Create role**. You’ll need to create two roles: one for `staging` users (we’ll call this role `staging_apm_viewer`) and one for `production` users (we’ll call this role `production_apm_viewer`). diff --git a/solutions/observability/apps/cross-cluster-search-with-application-data.md b/solutions/observability/apps/cross-cluster-search-with-application-data.md index dfdc278f9d..f676ac34d5 100644 --- a/solutions/observability/apps/cross-cluster-search-with-application-data.md +++ b/solutions/observability/apps/cross-cluster-search-with-application-data.md @@ -18,7 +18,7 @@ Elastic APM utilizes {{es}}'s cross-cluster search functionality. Cross-cluster If you’re using the Hosted {{ess}}, see [Enable cross-cluster search](../../../deploy-manage/remote-clusters/ec-enable-ccs.md). -To add remote clusters directly in {{kib}}, find `Remote Clusters` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). All you need is a name for the remote cluster and the seed node(s). Remember the names of your remote clusters, you’ll need them in step two. See [managing remote clusters](https://www.elastic.co/guide/en/elasticsearch/reference/current/ccr-getting-started-tutorial.html) for detailed information on the setup process. +To add remote clusters directly in {{kib}}, find `Remote Clusters` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). All you need is a name for the remote cluster and the seed node(s). Remember the names of your remote clusters, you’ll need them in step two. See [managing remote clusters](https://www.elastic.co/guide/en/elasticsearch/reference/current/ccr-getting-started-tutorial.html) for detailed information on the setup process. Alternatively, you can [configure remote clusters](https://www.elastic.co/guide/en/elasticsearch/reference/current/remote-clusters.html#configuring-remote-clusters) in {{es}}'s `elasticsearch.yml` file. @@ -32,7 +32,7 @@ You can also specify certain clusters to display data from, for example, `cluste There are two ways to edit the default {{data-source}}: -* In the Applications UI — Find **Applications** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Go to **Settings** → **Indices** and change all `xpack.apm.indices.*` values to include remote clusters. +* In the Applications UI — Find **Applications** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Go to **Settings** → **Indices** and change all `xpack.apm.indices.*` values to include remote clusters. * In `kibana.yml` — Update the [`xpack.apm.indices.*`](https://www.elastic.co/guide/en/kibana/current/apm-settings-kb.html) configuration values to include remote clusters. ::::{admonition} Exclude data tiers from search @@ -42,7 +42,7 @@ In a cross-cluster search (CCS) environment, it’s possible for different clust To prevent this, you can exclude [data tiers](../../../manage-data/lifecycle/data-tiers.md) that might slow down responses from search: the `data_frozen` and `data_cold` tiers. To exclude data tiers from search in the APM UI: -1. To open **Advanced settings**, find **Stack Management** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. To open **Advanced settings**, find **Stack Management** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. In the **Observability** section, update the **Excluded data tiers from search** option with a list of data tiers. :::: diff --git a/solutions/observability/apps/custom-filters.md b/solutions/observability/apps/custom-filters.md index 90b60e5567..71a507913f 100644 --- a/solutions/observability/apps/custom-filters.md +++ b/solutions/observability/apps/custom-filters.md @@ -57,7 +57,7 @@ To obfuscate the passwords stored in the request body, you can use a series of [ ### Create a pipeline [_create_a_pipeline] ::::{tip} -This tutorial uses the [Ingest APIs](https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest-apis.html), but it’s also possible to create a pipeline using the UI. In Kibana, go to **Stack Management** → **Ingest Pipelines** → **Create pipeline** → **New pipeline** or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +This tutorial uses the [Ingest APIs](https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest-apis.html), but it’s also possible to create a pipeline using the UI. In Kibana, go to **Stack Management** → **Ingest Pipelines** → **Create pipeline** → **New pipeline** or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). :::: diff --git a/solutions/observability/apps/fleet-managed-apm-server.md b/solutions/observability/apps/fleet-managed-apm-server.md index 20fe72245b..5fdadbe806 100644 --- a/solutions/observability/apps/fleet-managed-apm-server.md +++ b/solutions/observability/apps/fleet-managed-apm-server.md @@ -111,7 +111,7 @@ If you don’t have a {{fleet}} setup already in place, the easiest way to get s :::: -1. In {{kib}}, find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. In {{kib}}, find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Select **Elastic APM**. :::{image} ../../../images/observability-kibana-fleet-integrations-apm.png diff --git a/solutions/observability/apps/general-configuration-options.md b/solutions/observability/apps/general-configuration-options.md index 780bb62e95..21ca289f90 100644 --- a/solutions/observability/apps/general-configuration-options.md +++ b/solutions/observability/apps/general-configuration-options.md @@ -33,7 +33,7 @@ max_procs: 4 ::::::{tab-item} Fleet-managed Configure and customize Fleet-managed APM settings directly in {{kib}}: -1. In {{kib}}, find **Fleet** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. In {{kib}}, find **Fleet** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Under the **Agent policies** tab, select the policy you would like to configure. 3. Find the Elastic APM integration and select **Actions** > **Edit integration**. 4. Look for these settings under **General**. diff --git a/solutions/observability/apps/grant-access-using-api-keys.md b/solutions/observability/apps/grant-access-using-api-keys.md index 6510d24bbb..f66c74c0c2 100644 --- a/solutions/observability/apps/grant-access-using-api-keys.md +++ b/solutions/observability/apps/grant-access-using-api-keys.md @@ -19,7 +19,7 @@ For security reasons, we recommend using a unique API key per APM Server instanc To create an API key: -1. Go to **Stack Management** in the main menu and find **API Keys** or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Go to **Stack Management** in the main menu and find **API Keys** or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Create API key**. :::{image} ../../../images/observability-server-api-key-create.png @@ -86,7 +86,7 @@ output.elasticsearch: ## Create an API key for monitoring [apm-beats-api-key-monitor] -To open **API keys**, find **Stack Management** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Click **Create API key**. +To open **API keys**, find **Stack Management** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Click **Create API key**. :::{image} ../../../images/observability-server-api-key-create.png :alt: API key creation diff --git a/solutions/observability/apps/index-lifecycle-management.md b/solutions/observability/apps/index-lifecycle-management.md index 316cb358d1..56cdfe7409 100644 --- a/solutions/observability/apps/index-lifecycle-management.md +++ b/solutions/observability/apps/index-lifecycle-management.md @@ -62,7 +62,7 @@ This tutorial explains how to apply a custom index lifecycle policy to the `trac The **Data Streams** view in {{kib}} shows you data streams, index templates, and lifecycle policies: -1. To open **Index Management**, find **Stack Management** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. To open **Index Management**, find **Stack Management** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Select **Data Streams**. 3. Search for `traces-apm` to see all data streams associated with APM trace data. 4. In this example, I only have one data stream because I’m only using the `default` namespace. You may have more if your setup includes multiple namespaces. @@ -76,7 +76,7 @@ The **Data Streams** view in {{kib}} shows you data streams, index templates, an ## Step 2: Create an index lifecycle policy [apm-data-streams-custom-two] -1. To open **Lifecycle Policies**, find **Stack Management** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. To open **Lifecycle Policies**, find **Stack Management** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Create policy**. Name your new policy; For this tutorial, I’ve chosen `custom-traces-apm-policy`. Customize the policy to your liking, and when you’re done, click **Save policy**. diff --git a/solutions/observability/apps/integrate-with-jaeger-deprecated.md b/solutions/observability/apps/integrate-with-jaeger-deprecated.md index 7c03badc4c..a18f578a1d 100644 --- a/solutions/observability/apps/integrate-with-jaeger-deprecated.md +++ b/solutions/observability/apps/integrate-with-jaeger-deprecated.md @@ -50,7 +50,7 @@ The APM integration serves Jaeger gRPC over the same host and port as the Elasti ::::::{tab-item} Elasticsearch Service 1. Log into [{{ecloud}}](https://cloud.elastic.co?page=docs&placement=docs-body) and select your deployment. -2. In {{kib}}, find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +2. In {{kib}}, find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 3. Select **Elastic APM**. If the integration is already installed, under the polices tab, select **Actions*** > ***Edit integration**. If the integration has not been installed, select **Add Elastic APM**. Copy the URL. If you’re using Agent authorization, copy the Secret token as well. 4. Configure the APM Integration as a collector for your Jaeger agents. @@ -69,7 +69,7 @@ For the equivalent environment variables, change all letters to upper-case and r :::::: ::::::{tab-item} Self-managed -1. Configure the APM Integration as a collector for your Jaeger agents. In {{kib}}, find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Select **Elastic APM***. If the integration is already installed, under the polices tab, select ***Actions*** > ***Edit integration**. If the integration has not been installed, select **Add Elastic APM**. Copy the Host. If you’re using Agent authorization, copy the Secret token as well. +1. Configure the APM Integration as a collector for your Jaeger agents. In {{kib}}, find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Select **Elastic APM***. If the integration is already installed, under the polices tab, select ***Actions*** > ***Edit integration**. If the integration has not been installed, select **Add Elastic APM**. Copy the Host. If you’re using Agent authorization, copy the Secret token as well. As of this writing, the Jaeger agent binary offers the `--reporter.grpc.host-port` CLI flag. Use this to define the host and port that the APM Integration is listening on: diff --git a/solutions/observability/apps/inventory.md b/solutions/observability/apps/inventory.md index b78a1d6f81..a63444bdff 100644 --- a/solutions/observability/apps/inventory.md +++ b/solutions/observability/apps/inventory.md @@ -47,7 +47,7 @@ Inventory allows you to: ## Explore your entities [explore-your-entities] -1. To view all your entities, find **Inventory** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. To view all your entities, find **Inventory** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). When you open the Inventory for the first time, you’ll be asked to enable the EEM. Once enabled, the Inventory will be accessible to anyone with the appropriate privileges. diff --git a/solutions/observability/apps/secret-token.md b/solutions/observability/apps/secret-token.md index 190f8fa12b..c5fe346169 100644 --- a/solutions/observability/apps/secret-token.md +++ b/solutions/observability/apps/secret-token.md @@ -38,7 +38,7 @@ Create or update a secret token in {{fleet}}. Configure and customize Fleet-managed APM settings directly in {{kib}}: -1. In {{kib}}, find **Fleet** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. In {{kib}}, find **Fleet** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Under the **Agent policies** tab, select the policy you would like to configure. 3. Find the Elastic APM integration and select **Actions** > **Edit integration**. 4. Navigate to **Agent authorization** > **Secret token** and set the value of your token. diff --git a/solutions/observability/apps/tail-based-sampling.md b/solutions/observability/apps/tail-based-sampling.md index 8573dac95d..3fc340701c 100644 --- a/solutions/observability/apps/tail-based-sampling.md +++ b/solutions/observability/apps/tail-based-sampling.md @@ -37,7 +37,7 @@ max_procs: 4 ::::::{tab-item} Fleet-managed Configure and customize Fleet-managed APM settings directly in {{kib}}: -1. In {{kib}}, find **Fleet** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. In {{kib}}, find **Fleet** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Under the **Agent policies** tab, select the policy you would like to configure. 3. Find the Elastic APM integration and select **Actions** > **Edit integration**. 4. Look for these options under **Tail-based sampling**. diff --git a/solutions/observability/apps/view-elasticsearch-index-template.md b/solutions/observability/apps/view-elasticsearch-index-template.md index 21547acf80..3636ba80bd 100644 --- a/solutions/observability/apps/view-elasticsearch-index-template.md +++ b/solutions/observability/apps/view-elasticsearch-index-template.md @@ -7,7 +7,7 @@ mapped_pages: Index templates are used to configure the backing indices of data streams as they are created. These index templates are composed of multiple component templates—​reusable building blocks that configure index mappings, settings, and aliases. -The default APM index templates can be viewed in {{kib}}. To open **Index Management**, find **Stack Management** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Select **Index Templates** and search for `apm`. Select any of the APM index templates to view their relevant component templates. +The default APM index templates can be viewed in {{kib}}. To open **Index Management**, find **Stack Management** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Select **Index Templates** and search for `apm`. Select any of the APM index templates to view their relevant component templates. ## Edit the {{es}} index template [index-template-view] @@ -19,7 +19,7 @@ Custom index mappings may conflict with the mappings defined by the {{es}} apm-d The APM index templates by default reference a non-existent `@custom` component template for each data stream. You can create or edit this `@custom` component template to customize your {{es}} indices. -First, determine which [data stream](data-streams.md) you’d like to edit in {{kib}}. To open **Index Management**, find **Stack Management** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Select **Component Templates**. +First, determine which [data stream](data-streams.md) you’d like to edit in {{kib}}. To open **Index Management**, find **Stack Management** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Select **Component Templates**. Custom component templates are named following this pattern: `@custom`. Search for the name of the data stream, like `traces-apm`, and select its custom component template. Create one if it does not exist. In this example, that’d be, `traces-apm@custom`. Then click **Manage** → **Edit**. diff --git a/solutions/observability/cloud/gcp-dataflow-templates.md b/solutions/observability/cloud/gcp-dataflow-templates.md index 0b8251985a..e7e4f32e0e 100644 --- a/solutions/observability/cloud/gcp-dataflow-templates.md +++ b/solutions/observability/cloud/gcp-dataflow-templates.md @@ -25,7 +25,7 @@ Create a deployment using our hosted {{ess}} on [{{ecloud}}](https://cloud.elast You’ll start with installing the Elastic GCP integration to add pre-built dashboards, ingest node configurations, and other assets that help you get the most of the GCP logs you ingest. -1. Find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Search for `gcp`. :::{image} ../../../images/observability-monitor-gcp-kibana-integrations.png diff --git a/solutions/observability/cloud/monitor-amazon-cloud-compute-ec2.md b/solutions/observability/cloud/monitor-amazon-cloud-compute-ec2.md index 7d9425d7c4..a76efbcc23 100644 --- a/solutions/observability/cloud/monitor-amazon-cloud-compute-ec2.md +++ b/solutions/observability/cloud/monitor-amazon-cloud-compute-ec2.md @@ -28,7 +28,7 @@ Expand the **quick guide** to learn how, or skip to the next section if your dat :::::{dropdown} **Quick guide: Add data** ::::{admonition} -1. In the Observability UI, find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. In the Observability UI, find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. In the query bar, search for and select the **Amazon EC2** integration. 3. Read the overview to make sure you understand integration requirements and other considerations. 4. Click **Add Amazon EC2**. diff --git a/solutions/observability/cloud/monitor-amazon-kinesis-data-streams.md b/solutions/observability/cloud/monitor-amazon-kinesis-data-streams.md index 7ae4f3e873..effb3d43da 100644 --- a/solutions/observability/cloud/monitor-amazon-kinesis-data-streams.md +++ b/solutions/observability/cloud/monitor-amazon-kinesis-data-streams.md @@ -30,7 +30,7 @@ Expand the **quick guide** to learn how, or skip to the next section if your dat :::::{dropdown} **Quick guide: Add data** ::::{admonition} -1. In the Observability UI, find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. In the Observability UI, find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. In the query bar, search for and select the **Amazon Kinesis Data Stream** integration. 3. Read the overview to make sure you understand integration requirements and other considerations. 4. Click **Add Amazon Kinesis Data Stream**. diff --git a/solutions/observability/cloud/monitor-amazon-simple-queue-service-sqs.md b/solutions/observability/cloud/monitor-amazon-simple-queue-service-sqs.md index 52158f7703..c8b5e23b1a 100644 --- a/solutions/observability/cloud/monitor-amazon-simple-queue-service-sqs.md +++ b/solutions/observability/cloud/monitor-amazon-simple-queue-service-sqs.md @@ -26,7 +26,7 @@ Expand the **quick guide** to learn how, or skip to the next section if your dat :::::{dropdown} **Quick guide: Add data** ::::{admonition} -1. In the Observability UI, find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. In the Observability UI, find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. In the query bar, search for and select the **Amazon SQS** integration. 3. Read the overview to make sure you understand integration requirements and other considerations. 4. Click **Add Amazon SQS**. diff --git a/solutions/observability/cloud/monitor-amazon-simple-storage-service-s3.md b/solutions/observability/cloud/monitor-amazon-simple-storage-service-s3.md index 7769b0792c..6122489d10 100644 --- a/solutions/observability/cloud/monitor-amazon-simple-storage-service-s3.md +++ b/solutions/observability/cloud/monitor-amazon-simple-storage-service-s3.md @@ -29,7 +29,7 @@ Expand the **quick guide** to learn how, or skip to the next section if your dat :::::{dropdown} **Quick guide: Add data** ::::{admonition} -1. In the Observability UI, find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. In the Observability UI, find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. In the query bar, search for and select the **Amazon S3** integration. 3. Read the overview to make sure you understand integration requirements and other considerations. 4. Click **Add Amazon S3**. diff --git a/solutions/observability/cloud/monitor-amazon-web-services-aws-with-amazon-data-firehose.md b/solutions/observability/cloud/monitor-amazon-web-services-aws-with-amazon-data-firehose.md index 7693d42326..9a647d7362 100644 --- a/solutions/observability/cloud/monitor-amazon-web-services-aws-with-amazon-data-firehose.md +++ b/solutions/observability/cloud/monitor-amazon-web-services-aws-with-amazon-data-firehose.md @@ -29,7 +29,7 @@ Create a deployment in AWS regions (including gov cloud) using our hosted {{ess} ## Step 1: Install AWS integration in {{kib}} [firehose-step-one] -1. Install AWS integrations to load index templates, ingest pipelines, and dashboards into {{kib}}. Find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Find the AWS Integration by browsing the catalog. +1. Install AWS integrations to load index templates, ingest pipelines, and dashboards into {{kib}}. Find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Find the AWS Integration by browsing the catalog. 2. Navigate to the **Settings** tab and click **Install AWS assets**. Confirm by clicking **Install AWS** in the popup. 3. Install Amazon Data Firehose integration assets in Kibana. diff --git a/solutions/observability/cloud/monitor-amazon-web-services-aws-with-beats.md b/solutions/observability/cloud/monitor-amazon-web-services-aws-with-beats.md index 12f8dc4228..f6411d627b 100644 --- a/solutions/observability/cloud/monitor-amazon-web-services-aws-with-beats.md +++ b/solutions/observability/cloud/monitor-amazon-web-services-aws-with-beats.md @@ -174,7 +174,7 @@ Next, you are going to configure {{filebeat}} output to {{ess}}. echo -n "" | ./filebeat keystore add CLOUD_ID --stdin ``` -2. To store logs in {{es}} with minimal permissions, create an API key to send data from {{filebeat}} to {{ess}}. Log into {{kib}} (you can do so from the Cloud Console without typing in any permissions) and find `Dev Tools` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Send the following request: +2. To store logs in {{es}} with minimal permissions, create an API key to send data from {{filebeat}} to {{ess}}. Log into {{kib}} (you can do so from the Cloud Console without typing in any permissions) and find `Dev Tools` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Send the following request: ```console POST /_security/api_key @@ -358,9 +358,9 @@ Once you have edited the config file, you need to restart {{filebeat}}. To stop ## Step 6: Visualize Logs [aws-step-six] -Now that the logs are being shipped to {{es}} we can visualize them in {{kib}}. To see the raw logs, find **Discover** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +Now that the logs are being shipped to {{es}} we can visualize them in {{kib}}. To see the raw logs, find **Discover** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). -The filesets we used in the previous steps also come with pre-built dashboards that you can use to visualize the data. In {{kib}}, find **Dashboards** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Search for S3 and select the dashboard called: **[Filebeat AWS] S3 Server Access Log Overview**: +The filesets we used in the previous steps also come with pre-built dashboards that you can use to visualize the data. In {{kib}}, find **Dashboards** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Search for S3 and select the dashboard called: **[Filebeat AWS] S3 Server Access Log Overview**: :::{image} ../../../images/observability-S3-Server-Access-Logs.png :alt: S3 Server Access Log Overview @@ -442,7 +442,7 @@ Next, you are going to configure {{metricbeat}} output to {{ess}}. echo -n "" | ./metricbeat keystore add CLOUD_ID --stdin ``` -2. To store metrics in {{es}} with minimal permissions, create an API key to send data from {{metricbeat}} to {{ess}}. Log into {{kib}} (you can do so from the Cloud Console without typing in any permissions) and find `Dev Tools` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). From the **Console**, send the following request: +2. To store metrics in {{es}} with minimal permissions, create an API key to send data from {{metricbeat}} to {{ess}}. Log into {{kib}} (you can do so from the Cloud Console without typing in any permissions) and find `Dev Tools` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). From the **Console**, send the following request: ```console POST /_security/api_key @@ -568,13 +568,13 @@ You can now start {{metricbeat}}: ## Step 10: Visualize metrics [aws-step-ten] -Now that the metrics are being streamed to {{es}} we can visualize them in {{kib}}. To open **Infrastructure inventory**, find **Infrastructure*** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Make sure to show the ***AWS** source and the **EC2 Instances**: +Now that the metrics are being streamed to {{es}} we can visualize them in {{kib}}. To open **Infrastructure inventory**, find **Infrastructure*** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Make sure to show the ***AWS** source and the **EC2 Instances**: :::{image} ../../../images/observability-EC2-instances.png :alt: Your EC2 Infrastructure ::: -The metricsets we used in the previous steps also comes with pre-built dashboard that you can use to visualize the data. In {{kib}}, find **Dashboards** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Search for EC2 and select the dashboard called: **[Metricbeat AWS] EC2 Overview**: +The metricsets we used in the previous steps also comes with pre-built dashboard that you can use to visualize the data. In {{kib}}, find **Dashboards** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Search for EC2 and select the dashboard called: **[Metricbeat AWS] EC2 Overview**: :::{image} ../../../images/observability-ec2-dashboard.png :alt: EC2 Overview diff --git a/solutions/observability/cloud/monitor-amazon-web-services-aws-with-elastic-agent.md b/solutions/observability/cloud/monitor-amazon-web-services-aws-with-elastic-agent.md index 7a0389a320..bfd0e6fdaf 100644 --- a/solutions/observability/cloud/monitor-amazon-web-services-aws-with-elastic-agent.md +++ b/solutions/observability/cloud/monitor-amazon-web-services-aws-with-elastic-agent.md @@ -117,7 +117,7 @@ In this step, you install the AWS integration in {{kib}}. The AWS integration co To add the integration: -1. Find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. In the query bar, search for **AWS** and select the AWS integration to see more details about it. 3. Click **Add AWS**. 4. Configure the integration name and optionally add a description. @@ -227,7 +227,7 @@ Now you’re ready to edit the agent policy and configure S3 access log collecti The {{agent}} you’ve deployed is already running and collecting VPC flow logs. Now you need to edit the agent policy and configure the integration to collect S3 access logs. -1. In {{kib}}, find **Fleet** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. In {{kib}}, find **Fleet** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. On the **Agents** tab, click the policy your agent is using. 3. Edit the AWS integration policy and turn on the **Collect S3 access logs from S3** selector. 4. In the **Queue URL** field, enter the URL of the SQS queue you created for S3 access log notifications, then save and deploy your changes. @@ -237,7 +237,7 @@ It takes a few minutes for {{agent}} to update its configuration and start colle ## Step 5: Visualize AWS logs [aws-elastic-agent-visualize-logs] -Now that logs are streaming into {{es}}, you can visualize them in {{kib}}. To see the raw logs, find **Discover** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +Now that logs are streaming into {{es}}, you can visualize them in {{kib}}. To see the raw logs, find **Discover** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Notice that you can filter on a specific data stream. For example, set `data_stream.dataset : "aws.s3access"` to show S3 access logs. @@ -289,7 +289,7 @@ Extra AWS charges on CloudWatch API requests may be generated if you configure t } ``` -2. In {{kib}}, find **Fleet** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +2. In {{kib}}, find **Fleet** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 3. On the **Agents** tab, click the policy your agent is using. 4. Edit the AWS integration policy and turn on the **Collect billing metrics** selector. You can accept the defaults. 5. Also turn on the **Collect EC2 metrics** selector. Optionally change the defaults, then save and deploy your changes. @@ -299,14 +299,14 @@ It takes a few minutes for {{agent}} to update its configuration and start colle ## Step 7: Visualize AWS metrics [aws-elastic-agent-visualize-metrics] -Now that the metrics are streaming into {{es}}, you can visualize them in {{kib}}. Find **Discover** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Select the `metrics-*` data view, then filter on `data_stream.dataset: "aws.ec2_metrics"`: +Now that the metrics are streaming into {{es}}, you can visualize them in {{kib}}. Find **Discover** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Select the `metrics-*` data view, then filter on `data_stream.dataset: "aws.ec2_metrics"`: :::{image} ../../../images/observability-agent-tut-ec2-metrics-discover.png :alt: Screenshot of the Discover app showing EC2 metrics :class: screenshot ::: -The AWS integration also comes with pre-built dashboards that you can use to visualize the data. Find **Dashboards** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +The AWS integration also comes with pre-built dashboards that you can use to visualize the data. Find **Dashboards** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Search for EC2 and select the dashboard called **[Metrics AWS] EC2 Overview**: diff --git a/solutions/observability/cloud/monitor-amazon-web-services-aws-with-elastic-serverless-forwarder.md b/solutions/observability/cloud/monitor-amazon-web-services-aws-with-elastic-serverless-forwarder.md index 2033dd0444..68f8bbda54 100644 --- a/solutions/observability/cloud/monitor-amazon-web-services-aws-with-elastic-serverless-forwarder.md +++ b/solutions/observability/cloud/monitor-amazon-web-services-aws-with-elastic-serverless-forwarder.md @@ -94,7 +94,7 @@ For more details, refer to the AWS documentation on how to [Configure a bucket f {{kib}} offers prebuilt dashboards, ingest node configurations, and other assets that help you get the most value out of the logs you ingest. -1. Find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Search for AWS. 3. Click the AWS integration, select **Settings** and click **Install AWS assets** to install all the AWS integration assets. diff --git a/solutions/observability/cloud/monitor-aws-network-firewall-logs.md b/solutions/observability/cloud/monitor-aws-network-firewall-logs.md index 44e7109df1..43fe64a8e5 100644 --- a/solutions/observability/cloud/monitor-aws-network-firewall-logs.md +++ b/solutions/observability/cloud/monitor-aws-network-firewall-logs.md @@ -34,7 +34,7 @@ AWS PrivateLink is not supported. Make sure the deployment is on AWS, because th ## Step 1: Install AWS integration in {{kib}} [firehose-firewall-step-one] -1. Find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Browse the catalog to find the AWS integration. 3. Navigate to the **Settings** tab and click **Install AWS assets**. diff --git a/solutions/observability/cloud/monitor-cloudtrail-logs.md b/solutions/observability/cloud/monitor-cloudtrail-logs.md index f646e61b8a..0ff3100886 100644 --- a/solutions/observability/cloud/monitor-cloudtrail-logs.md +++ b/solutions/observability/cloud/monitor-cloudtrail-logs.md @@ -33,7 +33,7 @@ Make sure the deployment is on AWS, because the Amazon Data Firehose delivery st ## Step 1: Install AWS integration in {{kib}} [firehose-cloudtrail-step-one] -1. Find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Browse the catalog to find the Amazon Data Firehose integration. 3. Navigate to the **Settings** tab and click **Install Amazon Data Firehose assets**. diff --git a/solutions/observability/cloud/monitor-cloudwatch-logs.md b/solutions/observability/cloud/monitor-cloudwatch-logs.md index 9ab1adc5b9..a21da3d63d 100644 --- a/solutions/observability/cloud/monitor-cloudwatch-logs.md +++ b/solutions/observability/cloud/monitor-cloudwatch-logs.md @@ -35,7 +35,7 @@ AWS PrivateLink is not supported. Make sure the deployment is on AWS, because th ## Step 1: Install AWS integration in {{kib}} [firehose-cloudwatch-step-one] -1. Find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Browse the catalog to find the AWS integration. 3. Navigate to the **Settings** tab and click **Install AWS assets**. diff --git a/solutions/observability/cloud/monitor-google-cloud-platform-gcp.md b/solutions/observability/cloud/monitor-google-cloud-platform-gcp.md index 78526ede99..ba1bf69881 100644 --- a/solutions/observability/cloud/monitor-google-cloud-platform-gcp.md +++ b/solutions/observability/cloud/monitor-google-cloud-platform-gcp.md @@ -168,7 +168,7 @@ Next, you are going to configure {{metricbeat}} output to {{ess}}. echo -n "" | ./metricbeat keystore add CLOUD_ID --stdin ``` -2. To store metrics in {{es}} with minimal permissions, create an API key to send data from {{metricbeat}} to {{ess}}. Log into {{kib}} (you can do so from the Cloud Console without typing in any permissions) and find `Dev Tools` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). From the **Console**, send the following request: +2. To store metrics in {{es}} with minimal permissions, create an API key to send data from {{metricbeat}} to {{ess}}. Log into {{kib}} (you can do so from the Cloud Console without typing in any permissions) and find `Dev Tools` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). From the **Console**, send the following request: ```console POST /_security/api_key @@ -339,7 +339,7 @@ Next, you are going to configure {{filebeat}} output to {{ess}}. echo -n "" | ./filebeat keystore add CLOUD_ID --stdin ``` -2. To store logs in {{es}} with minimal permissions, create an API key to send data from {{filebeat}} to {{ess}}. Log into {{kib}} (you can do so from the Cloud Console without typing in any permissions) and find `Dev Tools` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Send the following request: +2. To store logs in {{es}} with minimal permissions, create an API key to send data from {{filebeat}} to {{ess}}. Log into {{kib}} (you can do so from the Cloud Console without typing in any permissions) and find `Dev Tools` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Send the following request: ```console POST /_security/api_key diff --git a/solutions/observability/cloud/monitor-microsoft-azure-openai.md b/solutions/observability/cloud/monitor-microsoft-azure-openai.md index 6808bb5225..ee10a3eb74 100644 --- a/solutions/observability/cloud/monitor-microsoft-azure-openai.md +++ b/solutions/observability/cloud/monitor-microsoft-azure-openai.md @@ -156,7 +156,7 @@ To add a role assignment to your app: ## Step 3: Configure the Azure OpenAI integration [azure-openai-configure-integration] -1. Find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. In the query bar, search for **Azure OpenAI** and select the Azure OpenAI integration card. 3. Click **Add Azure OpenAI**. 4. Under Integration settings, configure the integration name and optionally add a description. @@ -251,7 +251,7 @@ Now that your log and metric data is streaming to {{es}}, you can view them in { The Elastic Azure OpenAI integration comes with a built-in overview dashboard to visualize your log and metric data. To view the integration dashboards: -1. Find **Dashboards** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Dashboards** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Search for **Azure OpenAI**. 3. Select the `[Azure OpenAI] Overview` dashboard. @@ -264,7 +264,7 @@ For more on dashboards and visualization, refer to the [Dashboards and visualiza ### View logs and metrics with Discover [azure-openai-discover] -Find **Discover** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). From the data view drop-down, select either `logs-*` or `metrics-*` to view specific data. You can also create data views if, for example, you wanted to view both `logs-*` and `metrics-*` simultaneously. +Find **Discover** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). From the data view drop-down, select either `logs-*` or `metrics-*` to view specific data. You can also create data views if, for example, you wanted to view both `logs-*` and `metrics-*` simultaneously. ![screenshot of the Discover data view dropdown](../../../images/observability-discover-data-view-menu.png "") @@ -280,7 +280,7 @@ For more on using Discover and creating data views, refer to the [Discover](../. ### View logs with Logs Explorer [azure-openai-logs-explorer] -To view Azure OpenAI logs, open {{kib}} and go to **Logs Explorer** (find `Logs Explorer` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search)). With **Logs Explorer**, you can quickly search and filter your log data, get information about the structure of log fields, and display your findings in a visualization. +To view Azure OpenAI logs, open {{kib}} and go to **Logs Explorer** (find `Logs Explorer` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md)). With **Logs Explorer**, you can quickly search and filter your log data, get information about the structure of log fields, and display your findings in a visualization. :::{image} ../../../images/observability-log-explorer.png :alt: screenshot of the logs explorer main page @@ -310,7 +310,7 @@ For this tutorial, we’ll be using an [example Python application](https://gith To start collecting APM data for your Azure OpenAI applications, gather the OpenTelemetry OTLP exporter endpoint and authentication header from your {{ecloud}} instance: -1. Find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Select the **APM** integration. 3. Scroll down to **APM Agents** and select the **OpenTelemetry** tab. 4. Make note of the configuration values for the following configuration settings: diff --git a/solutions/observability/cloud/monitor-microsoft-azure-with-azure-native-isv-service.md b/solutions/observability/cloud/monitor-microsoft-azure-with-azure-native-isv-service.md index 24b89d220e..62f7efcf3c 100644 --- a/solutions/observability/cloud/monitor-microsoft-azure-with-azure-native-isv-service.md +++ b/solutions/observability/cloud/monitor-microsoft-azure-with-azure-native-isv-service.md @@ -95,7 +95,7 @@ To ingest Azure subscription and resource logs into Elastic, you use the Azure N Native metrics collection for Azure services is not fully supported yet. To learn how to collect metrics from Azure services, refer to [Monitor Microsoft Azure with {{agent}}](monitor-microsoft-azure-with-elastic-agent.md). :::: -3. In {{kib}}, under **{{observability}}**, find **Overview** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Refresh the page until you see some data. This may take a few minutes. +3. In {{kib}}, under **{{observability}}**, find **Overview** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Refresh the page until you see some data. This may take a few minutes. 4. To analyze your subscription and resource logs, click **Show Logs Explorer**. @@ -111,7 +111,7 @@ To ingest Azure subscription and resource logs into Elastic, you use the Azure N 3. Wait until the extension is installed and sending data (if the list does not update, click **Refresh** ). 4. Back in {{kib}}, view the **Logs Explorer** again. Notice that you can filter the view to show logs for a specific instance, for example `cloud.instance.name : "ingest-tutorial-linux"`. -5. To view VM metrics, go to **Infrastructure inventory** and then select a VM. (To open **Infrastructure inventory**, find **Infrastructure** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search).) +5. To view VM metrics, go to **Infrastructure inventory** and then select a VM. (To open **Infrastructure inventory**, find **Infrastructure** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).) To explore the data further, click **Open as page**. diff --git a/solutions/observability/cloud/monitor-microsoft-azure-with-beats.md b/solutions/observability/cloud/monitor-microsoft-azure-with-beats.md index 63a51e530f..ce7274c138 100644 --- a/solutions/observability/cloud/monitor-microsoft-azure-with-beats.md +++ b/solutions/observability/cloud/monitor-microsoft-azure-with-beats.md @@ -88,7 +88,7 @@ To ingest Azure subscription and resource logs into Elastic using the Microsoft :::: -3. In {{kib}}, find the {{observability}} **Overview** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Refresh the page until you see some data. This may take a few minutes. +3. In {{kib}}, find the {{observability}} **Overview** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Refresh the page until you see some data. This may take a few minutes. 4. To analyze your subscription and resource logs, click **Show Logs Explorer**. @@ -102,9 +102,9 @@ To ingest Azure subscription and resource logs into Elastic using the Microsoft ![Select VMs to collect logs and metrics from](../../../images/observability-monitor-azure-elastic-vms.png "") -3. Wait until it is installed and sending data (if the list does not update, click **Refresh** ). To see the logs from the VM, open **Logs Explorer** (find `Logs Explorer` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search)). +3. Wait until it is installed and sending data (if the list does not update, click **Refresh** ). To see the logs from the VM, open **Logs Explorer** (find `Logs Explorer` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md)). - To view VM metrics, go to **Infrastructure inventory** and then select a VM. (To open **Infrastructure inventory**, find **Infrastructure** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search).) + To view VM metrics, go to **Infrastructure inventory** and then select a VM. (To open **Infrastructure inventory**, find **Infrastructure** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).) ::::{note} @@ -246,7 +246,7 @@ Next, you are going to configure {{metricbeat}} output to {{ess}}. echo -n "" | ./metricbeat keystore add CLOUD_ID --stdin ``` -2. To store metrics in {{es}} with minimal permissions, create an API key to send data from {{metricbeat}} to {{ess}}. Log into {{kib}} (you can do so from the Cloud Console without typing in any permissions) and find `Dev Tools` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). From the **Console**, send the following request: +2. To store metrics in {{es}} with minimal permissions, create an API key to send data from {{metricbeat}} to {{ess}}. Log into {{kib}} (you can do so from the Cloud Console without typing in any permissions) and find `Dev Tools` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). From the **Console**, send the following request: ```console POST /_security/api_key diff --git a/solutions/observability/cloud/monitor-microsoft-azure-with-elastic-agent.md b/solutions/observability/cloud/monitor-microsoft-azure-with-elastic-agent.md index f576bd4e85..b6d0e1f6bc 100644 --- a/solutions/observability/cloud/monitor-microsoft-azure-with-elastic-agent.md +++ b/solutions/observability/cloud/monitor-microsoft-azure-with-elastic-agent.md @@ -90,7 +90,7 @@ In this step, you install the Azure Billing Metrics integration in {{kib}}. This To add the integration: -1. Find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. In the query bar, search for **Azure Billing** and select the Azure Billing Metrics integration to see more details about it. 3. Click **Add Azure Billing Metrics**. 4. Under Integration settings, configure the integration name and optionally add a description. @@ -157,7 +157,7 @@ It takes a few minutes for {{agent}} to enroll in {{fleet}}, download the config ## Step 4: Visualize Azure billing metrics [azure-elastic-agent-visualize-metrics] -Now that the metrics are streaming to {{es}}, you can visualize them in {{kib}}. Find **Dashboards** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Search for Azure Billing and select the dashboard called **[Azure Billing] Billing Overview**. +Now that the metrics are streaming to {{es}}, you can visualize them in {{kib}}. Find **Dashboards** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Search for Azure Billing and select the dashboard called **[Azure Billing] Billing Overview**. :::{image} ../../../images/observability-agent-tut-azure-billing-dashboard.png :alt: Screenshot of Azure billing overview dashboard @@ -243,7 +243,7 @@ Now that activity logs are streaming into the event hub, you can configure the A To add the integration: -1. Find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. In the query bar, search for **Azure activity logs** and select the Azure activity logs integration to see more details about it. 3. Click **Add Azure activity logs**. 4. Under Integration settings, configure the integration name and optionally add a description. @@ -281,7 +281,7 @@ To add the integration: ## Step 5: Visualize Azure activity logs [azure-elastic-agent-visualize-azure-logs] -Now that logs are streaming into {{es}}, you can visualize them in {{kib}}. To see the raw logs, find **Discover** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Notice that you can filter on a specific data stream. For example, you can use `data_stream.dataset : "azure.activitylogs"` to show Azure activity logs. +Now that logs are streaming into {{es}}, you can visualize them in {{kib}}. To see the raw logs, find **Discover** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Notice that you can filter on a specific data stream. For example, you can use `data_stream.dataset : "azure.activitylogs"` to show Azure activity logs. The Azure activity logs integration also comes with pre-built dashboards that you can use to visualize the data. In {{kib}}, open the main menu and click **Dashboard**. Search for Azure activity and select the dashboard called **[Logs Azure] User Activity**: diff --git a/solutions/observability/cloud/monitor-web-application-firewall-waf-logs.md b/solutions/observability/cloud/monitor-web-application-firewall-waf-logs.md index f72073ea1e..f7f34d2140 100644 --- a/solutions/observability/cloud/monitor-web-application-firewall-waf-logs.md +++ b/solutions/observability/cloud/monitor-web-application-firewall-waf-logs.md @@ -35,7 +35,7 @@ Make sure the deployment is on AWS, because the Amazon Data Firehose delivery st ## Step 1: Install the AWS integration in {{kib}} [firehose-waf-step-one] -1. Find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Browse the catalog to find the AWS integration. 3. Navigate to the **Settings** tab and click **Install AWS assets**. diff --git a/solutions/observability/get-started/add-data-from-splunk.md b/solutions/observability/get-started/add-data-from-splunk.md index 225a4f7c5f..b445e0ba38 100644 --- a/solutions/observability/get-started/add-data-from-splunk.md +++ b/solutions/observability/get-started/add-data-from-splunk.md @@ -36,7 +36,7 @@ To get started quickly, spin up a deployment of our hosted {{ess}}. The {{ess}} ## Step 1: Add integration [splunk-step-one] -Find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Search for and add the nginx integration. Refer to [Get started with system metrics](../infra-and-hosts/get-started-with-system-metrics.md) for detailed steps about adding integrations. +Find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Search for and add the nginx integration. Refer to [Get started with system metrics](../infra-and-hosts/get-started-with-system-metrics.md) for detailed steps about adding integrations. ## Step 2: Enable Collect logs from third-party REST API [splunk-step-two] diff --git a/solutions/observability/incident-management/configure-service-level-objective-slo-access.md b/solutions/observability/incident-management/configure-service-level-objective-slo-access.md index 772958de8b..953ab24e65 100644 --- a/solutions/observability/incident-management/configure-service-level-objective-slo-access.md +++ b/solutions/observability/incident-management/configure-service-level-objective-slo-access.md @@ -31,7 +31,7 @@ You can enable access to SLOs in two different ways: To create a role: -1. To open **Roles**, find **Stack Management** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. To open **Roles**, find **Stack Management** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. On the **Roles** page, click **Create role**. diff --git a/solutions/observability/infra-and-hosts/explore-infrastructure-metrics-over-time.md b/solutions/observability/infra-and-hosts/explore-infrastructure-metrics-over-time.md index f1666efa99..86bb899a1c 100644 --- a/solutions/observability/infra-and-hosts/explore-infrastructure-metrics-over-time.md +++ b/solutions/observability/infra-and-hosts/explore-infrastructure-metrics-over-time.md @@ -9,7 +9,7 @@ The **Metrics Explorer** page enables you to create time-series visualizations b Additionally, for detailed analyses of your metrics, you can annotate and save visualizations for your custom dashboards by using the [Time Series Visual Builder (TSVB)](https://www.elastic.co/guide/en/kibana/current/legacy-editors.html#tsvb-panel) within {{kib}}. -To open **Metrics Explorer**, find **Infrastructure** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +To open **Metrics Explorer**, find **Infrastructure** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). :::{image} ../../../images/observability-metrics-explorer.png :alt: Metrics Explorer diff --git a/solutions/observability/infra-and-hosts/tutorial-observe-kubernetes-deployments.md b/solutions/observability/infra-and-hosts/tutorial-observe-kubernetes-deployments.md index f2b43534fa..ca410b0739 100644 --- a/solutions/observability/infra-and-hosts/tutorial-observe-kubernetes-deployments.md +++ b/solutions/observability/infra-and-hosts/tutorial-observe-kubernetes-deployments.md @@ -86,7 +86,7 @@ To start collecting logs and metrics from your Kubernetes clusters, first add th Follow these steps to add the Kubernetes integration to your policy: -1. Find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Enter "Kubernetes" in the search bar, and select the **Kubernetes** integration. 3. Click **Add Kubernetes** at the top of the Kubernetes integration page. 4. Click **Add integration only (skip agent installation)** at the bottom of the Add integration page. @@ -494,7 +494,7 @@ Use {{kib}} to view the metric and log data collected by {{agent}}. Refer to the ### View performance and health metrics [monitor-k8s-explore-metrics] -To view the performance and health metrics collected by {{agent}}, find **Infrastructure** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +To view the performance and health metrics collected by {{agent}}, find **Infrastructure** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). On the **Infrastructure inventory** page, you can switch between different views to see an overview of the containers and pods running on Kubernetes: @@ -517,7 +517,7 @@ For more on using the **Metrics Explorer** page, refer to [Explore infrastructur ### View Kubernetes logs [monitor-k8s-explore-logs] -Find `Logs Explorer` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +Find `Logs Explorer` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). With **Logs Explorer**, you can quickly search and filter your log data, get information about the structure of log fields, and display your findings in a visualization. @@ -565,7 +565,7 @@ If you want to manage APM yourself, there are a few alternative options: A [secret token](../apps/secret-token.md) is used to secure communication between APM agents and APM Server. To create or update your secret token in {{kib}}: -1. Find **Fleet** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Fleet** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Under the **Agent policies** tab, select the policy you would like to configure. 3. Find the Elastic APM integration and select **Actions → Edit integration**. 4. Navigate to **Agent authorization → Secret token** and set the value of your token. @@ -1161,7 +1161,7 @@ kubectl apply -f demo.yml ### View your application’s traces in {{kib}} [_view_your_applications_traces_in_kib] -Application trace data is available in the **Service Inventory**. To open **Service Inventory**, find **Applications** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +Application trace data is available in the **Service Inventory**. To open **Service Inventory**, find **Applications** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). The **Applications** app allows you to monitor your software services and applications in real-time: visualize detailed performance information on your services, identify and analyze errors, and monitor host-level and agent-specific metrics like JVM and Go runtime metrics. diff --git a/solutions/observability/infra-and-hosts/tutorial-observe-nginx-instances.md b/solutions/observability/infra-and-hosts/tutorial-observe-nginx-instances.md index ce18075e37..541c0b6bcc 100644 --- a/solutions/observability/infra-and-hosts/tutorial-observe-nginx-instances.md +++ b/solutions/observability/infra-and-hosts/tutorial-observe-nginx-instances.md @@ -56,7 +56,7 @@ Before you can monitor nginx, you need the following: Follow these steps to add the nginx integration to your deployment: -1. Find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Enter "nginx" in the search bar, and select the **Nginx** integration. 3. Select **Add Nginx** at the top of the integration page. 4. Select **Add integration only (skip agent installation)** at the bottom of the page. @@ -120,7 +120,7 @@ Follow the instructions from the **Add agent** screen to install the {{agent}} o Before installing and running the standalone {{agent}}, you need to create an API key. To create an {{ecloud}} API key: -1. To open **API keys**, find **Stack Management** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. To open **API keys**, find **Stack Management** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Select **Create API key**. 3. Give the key a name. For example, `nginx API key`. 4. Leave the other default options and select **Create API key**. @@ -180,7 +180,7 @@ Use {{kib}} to view the metric and log data collected by {{agent}}. Refer to the The nginx integration has a built-in dashboard that shows the full picture of your nginx metrics in one place. To open the nginx dashboard: -1. Find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Select **Installed integrations**. 3. Select the **Nginx** card and open the **Assets** tab. 4. Select either the `[Metrics Nginx] Overview` dashboard. @@ -202,7 +202,7 @@ After your nginx logs are ingested, view and explore your logs using [Logs Explo With Logs Explorer, you can quickly search and filter your log data, get information about the structure of log fields, and display your findings in a visualization. -To open **Logs Explorer**, find `Logs Explorer` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +To open **Logs Explorer**, find `Logs Explorer` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Filter your results to see logs from the nginx integration from the data selector: @@ -227,7 +227,7 @@ The **Documents** table now shows your nginx logs: The nginx integration has built-in dashboards that show the full picture of your nginx logs in one place. To open the nginx dashboards: -1. Find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Select **Installed integrations**. 3. Select the **Nginx** card and open the **Assets** tab. 4. Select either the `[Logs Nginx] Overview` dashboard or the `[Logs Nginx] Access and error logs` dashboard. @@ -293,7 +293,7 @@ Verify that your environment is set up properly to use the {{ml-features}}. If { Add the nginx ML jobs from the nginx integration to start using anomaly detection: -* To open **Jobs**, find **Machine Learning** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +* To open **Jobs**, find **Machine Learning** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 1. Select **Create job**. 2. In the search bar, enter **nginx** and select **Nginx access logs [Logs Nginx]**. diff --git a/solutions/observability/infra-and-hosts/universal-profiling-index-life-cycle-management.md b/solutions/observability/infra-and-hosts/universal-profiling-index-life-cycle-management.md index 25b6d4f9d1..a95bf686a9 100644 --- a/solutions/observability/infra-and-hosts/universal-profiling-index-life-cycle-management.md +++ b/solutions/observability/infra-and-hosts/universal-profiling-index-life-cycle-management.md @@ -45,7 +45,7 @@ Complete the following steps to configure a custom index lifecycle policy. ### Step 1: Create an index lifecycle policy [profiling-ilm-custom-policy-create-policy] -1. To open **Index Lifecycle Policies**, find **Stack Management** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. To open **Index Lifecycle Policies**, find **Stack Management** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Create policy**. 3. Name your new policy, for example `custom-profiling-policy`. 4. Customize the policy to your liking. @@ -93,7 +93,7 @@ To apply a custom {{ilm-init}} policy, you must name the component template `pro Confirm that Universal Profiling is now using the new index template and {{ilm-init}} policy: -1. Open **Console** by finding `Dev Tools` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Open **Console** by finding `Dev Tools` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Run the following: ```bash diff --git a/solutions/observability/infra-and-hosts/universal-profiling.md b/solutions/observability/infra-and-hosts/universal-profiling.md index e72b68d8fd..c610e28ce1 100644 --- a/solutions/observability/infra-and-hosts/universal-profiling.md +++ b/solutions/observability/infra-and-hosts/universal-profiling.md @@ -16,7 +16,7 @@ On this page, you’ll find information on: ## Inspecting data in {{kib}} [profiling-inspecting-data-in-kibana] -To open **Universal Profiling**, find **Infrastructure** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +To open **Universal Profiling**, find **Infrastructure** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Under **Universal Profiling**, click **Stacktraces** to open the [stacktraces view](#profiling-stacktraces-intro). diff --git a/solutions/observability/infra-and-hosts/upgrade-universal-profiling.md b/solutions/observability/infra-and-hosts/upgrade-universal-profiling.md index 53fd96a281..381c2119ee 100644 --- a/solutions/observability/infra-and-hosts/upgrade-universal-profiling.md +++ b/solutions/observability/infra-and-hosts/upgrade-universal-profiling.md @@ -63,7 +63,7 @@ When stopping incoming requests, Universal Profiling Agent replicas back off and You can delete existing profiling data in Kibana: -1. If you’re upgrading from 8.9.0 or later, go to **Console** and execute the following snippet. (To open **Console**, find `Dev Tools` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search).) If you’re upgrading from an earlier version, skip this step. +1. If you’re upgrading from 8.9.0 or later, go to **Console** and execute the following snippet. (To open **Console**, find `Dev Tools` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).) If you’re upgrading from an earlier version, skip this step. ```console PUT /_cluster/settings @@ -74,7 +74,7 @@ You can delete existing profiling data in Kibana: } ``` -2. Open **Index Management** by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +2. Open **Index Management** by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 3. Make sure you’re in the **Data Streams** tab, and search for `profiling-` in the search bar. 4. Select all resulting data streams, and click the **Delete data streams** button. 5. Switch to the **Indices** tab, enable **Include hidden indices**, and search for `profiling-` in the search bar. diff --git a/solutions/observability/logs/categorize-log-entries.md b/solutions/observability/logs/categorize-log-entries.md index 2dd463e20d..4e2e3c8844 100644 --- a/solutions/observability/logs/categorize-log-entries.md +++ b/solutions/observability/logs/categorize-log-entries.md @@ -19,9 +19,9 @@ This feature makes use of {{ml}} {anomaly-jobs}. To set up jobs, you must have ` Create a {{ml}} job to categorize log messages automatically. {{ml-cap}} observes the static parts of the message, clusters similar messages, classifies them into message categories, and detects unusually high message counts in the categories. -1. Open the **Categories** page by finding `Logs / Categories` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). You are prompted to use {{ml}} to create log rate categorizations. +1. Open the **Categories** page by finding `Logs / Categories` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). You are prompted to use {{ml}} to create log rate categorizations. 2. Choose a time range for the {{ml}} analysis. By default, the {{ml}} job analyzes log messages no older than four weeks and continues indefinitely. -3. Add the indices that contain the logs you want to examine. By default, Machine Learning analyzes messages in all log indices that match the patterns set in the **logs sources** advanced setting. To open **Advanced settings**, find **Stack Management** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +3. Add the indices that contain the logs you want to examine. By default, Machine Learning analyzes messages in all log indices that match the patterns set in the **logs sources** advanced setting. To open **Advanced settings**, find **Stack Management** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 4. Click **Create ML job**. The job is created, and it starts to run. It takes a few minutes for the {{ml}} robots to collect the necessary data. After the job processed the data, you can view the results. diff --git a/solutions/observability/logs/configure-data-sources.md b/solutions/observability/logs/configure-data-sources.md index bcd11db60a..7eb0abdf74 100644 --- a/solutions/observability/logs/configure-data-sources.md +++ b/solutions/observability/logs/configure-data-sources.md @@ -20,12 +20,12 @@ If your logs have custom index patterns, use non-default field settings, or cont ## Edit configuration settings [edit-config-settings] -1. Find `Logs / Settings` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find `Logs / Settings` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). | | | | --- | --- | | **Name** | Name of the source configuration. | - | **{{kib}} log sources advanced setting** | Use index patterns stored in the {{kib}} **log sources** advanced setting, which provides a centralized place to store and query log index patterns.To open **Advanced settings**, find **Stack Management** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). | + | **{{kib}} log sources advanced setting** | Use index patterns stored in the {{kib}} **log sources** advanced setting, which provides a centralized place to store and query log index patterns.To open **Advanced settings**, find **Stack Management** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). | | **{{data-source-cap}} (deprecated)** | The Logs UI integrates with {{data-sources}} toconfigure the used indices by clicking **Use {{data-sources}}**. | | **Log indices (deprecated)** | {{kib}} index patterns or index name patterns in the {{es}} indicesto read log data from. | | **Log columns** | Columns that are displayed in the logs **Stream** page. | diff --git a/solutions/observability/logs/explore-logs.md b/solutions/observability/logs/explore-logs.md index 4b6f320f5a..0cc069b6b0 100644 --- a/solutions/observability/logs/explore-logs.md +++ b/solutions/observability/logs/explore-logs.md @@ -11,7 +11,7 @@ Logs Explorer allows you to quickly search and filter your log data, get informa Logs Explorer also provides {{ml}} to detect specific [log anomalies](inspect-log-anomalies.md) automatically and [categorize log messages](categorize-log-entries.md) to quickly identify patterns in your log events. -To view Logs Explorer, find `Logs Explorer` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search)) +To view Logs Explorer, find `Logs Explorer` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md)) diff --git a/solutions/observability/logs/inspect-log-anomalies.md b/solutions/observability/logs/inspect-log-anomalies.md index 0becb76f1a..4344d0aaf8 100644 --- a/solutions/observability/logs/inspect-log-anomalies.md +++ b/solutions/observability/logs/inspect-log-anomalies.md @@ -26,7 +26,7 @@ Create a {{ml}} job to detect anomalous log entry rates automatically. 1. Select **Anomalies**, and you’ll be prompted to create a {{ml}} job which will carry out the log rate analysis. 2. Choose a time range for the {{ml}} analysis. -3. Add the indices that contain the logs you want to examine. By default, Machine Learning analyzes messages in all log indices that match the patterns set in the **logs source** advanced setting. To open **Advanced settings**, find **Stack Management** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +3. Add the indices that contain the logs you want to examine. By default, Machine Learning analyzes messages in all log indices that match the patterns set in the **logs source** advanced setting. To open **Advanced settings**, find **Stack Management** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 4. Click **Create {{ml-init}} job**. 5. You’re now ready to explore your log partitions. diff --git a/solutions/observability/logs/logs-stream.md b/solutions/observability/logs/logs-stream.md index 18aa4bd8fd..8e88982b41 100644 --- a/solutions/observability/logs/logs-stream.md +++ b/solutions/observability/logs/logs-stream.md @@ -22,7 +22,7 @@ Click **Stream Live** to view a continuous flow of log messages in real time, or Because [Logs Explorer](logs-explorer.md) is replacing Logs Stream, Logs Stream and the Logs Stream dashboard panel are disabled by default. To activate Logs Stream and the Logs Stream dashboard panel complete the following steps: -1. To open **Advanced Settings**, find **Stack Management** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. To open **Advanced Settings**, find **Stack Management** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. In **Advanced Settings**, enter *Logs Stream* in the search bar. 3. Turn on **Logs Stream**. diff --git a/solutions/observability/observability-ai-assistant.md b/solutions/observability/observability-ai-assistant.md index c83350a38c..ffab08011c 100644 --- a/solutions/observability/observability-ai-assistant.md +++ b/solutions/observability/observability-ai-assistant.md @@ -127,7 +127,7 @@ You can also add information to the knowledge base by asking the AI Assistant to To add external data to the knowledge base in {{kib}}: -1. To open AI Assistant settings, find `AI Assistants` in the [global search field](../../get-started/the-stack.md#kibana-navigation-search). +1. To open AI Assistant settings, find `AI Assistants` in the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Under **Elastic AI Assistant for Observability**, click **Manage settings**. 3. Switch to the **Knowledge base** tab. 4. Click the **New entry** button, and choose either: @@ -162,7 +162,7 @@ By default, the AI Assistant queries all search connector indices. To override t To create a connector in the {{kib}} UI and make its content available to the AI Assistant knowledge base, follow these steps: -1. Open **Connectors** by finding `Content / Connectors` in the [global search field](../../get-started/the-stack.md#kibana-navigation-search). +1. Open **Connectors** by finding `Content / Connectors` in the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md). ::::{note} If your {{kib}} Space doesn’t include the Search solution you will have to create the connector from a different space or change your space **Solution view** setting to `Classic`. @@ -386,7 +386,7 @@ To learn more about alerting, actions, and connectors, refer to [Alerting](incid To access the AI Assistant Settings page, you can: -* Find `AI Assistants` in the [global search field](../../get-started/the-stack.md#kibana-navigation-search). +* Find `AI Assistants` in the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md). * Use the **More actions** menu inside the AI Assistant window. The AI Assistant Settings page contains the following tabs: diff --git a/solutions/observability/unknown-bucket/logs-index-template-reference.md b/solutions/observability/unknown-bucket/logs-index-template-reference.md index 8c9f36d217..c4bb01db24 100644 --- a/solutions/observability/unknown-bucket/logs-index-template-reference.md +++ b/solutions/observability/unknown-bucket/logs-index-template-reference.md @@ -7,7 +7,7 @@ mapped_pages: Index templates are used to configure the backing indices of data streams as they’re created. These index templates are composed of multiple [component templates](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-component-template.html)—reusable building blocks that configure index mappings, settings, and aliases. -You can view the default `logs` index template in {{kib}}. To open **Index Management**, find **Stack Management** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Select **Index Templates** and search for `logs`. Select the `logs` index templates to view relevant component templates. +You can view the default `logs` index template in {{kib}}. To open **Index Management**, find **Stack Management** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Select **Index Templates** and search for `logs`. Select the `logs` index templates to view relevant component templates. ## Edit the `logs` index template [custom-logs-template-edit] @@ -21,7 +21,7 @@ The default `logs` index template for the `logs-*-*` index pattern is composed o You can use the `logs@custom` component template to customize your {{es}} indices. The `logs@custom` component template is not installed by default, but you can create a component template named `logs@custom` to override and extend default mappings or settings. To do this: -1. To open **Index Management**, find **Stack Management** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. To open **Index Management**, find **Stack Management** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Select **Component Templates**. 3. Click **Create component template**. 4. Name the component template logs@custom. @@ -40,7 +40,7 @@ The `logs` index template uses `default_field: [*]` meaning queries without spec If you haven’t already created the `logs@custom`component template, create it as outlined in the previous section. Then, follow these steps to update the **Index settings** of the component template: -1. To open **Index Management**, find **Stack Management** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. To open **Index Management**, find **Stack Management** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Select **Component Templates**. 3. Search for `logs` and find the `logs@custom` component template. 4. Open the **Actions** menu and select **Edit**. diff --git a/solutions/observability/unknown-bucket/monitor-aws-with-amazon-data-firehose.md b/solutions/observability/unknown-bucket/monitor-aws-with-amazon-data-firehose.md index 59d0abc153..daa5dc578b 100644 --- a/solutions/observability/unknown-bucket/monitor-aws-with-amazon-data-firehose.md +++ b/solutions/observability/unknown-bucket/monitor-aws-with-amazon-data-firehose.md @@ -29,7 +29,7 @@ Create a deployment in AWS regions (including gov cloud) using our hosted {{ess} ## Step 1: Install AWS integration in {{kib}} [firehose-step-one] -1. Install AWS integrations to load index templates, ingest pipelines, and dashboards into {{kib}}. Find **Integrations** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Find the AWS Integration by browsing the catalog. +1. Install AWS integrations to load index templates, ingest pipelines, and dashboards into {{kib}}. Find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Find the AWS Integration by browsing the catalog. 2. Navigate to the **Settings** tab and click **Install AWS assets**. Confirm by clicking **Install AWS** in the popup. 3. Install Amazon Data Firehose integration assets in Kibana. diff --git a/solutions/search/search-connection-details.md b/solutions/search/search-connection-details.md index 48fc0bb424..5e3a32dbe8 100644 --- a/solutions/search/search-connection-details.md +++ b/solutions/search/search-connection-details.md @@ -37,7 +37,7 @@ To connect to your {{es}} deployment, you need either a Cloud ID or an {{es}} en ### Create an API key [create-an-api-key-cloud-self-managed] -1. To navigate to **API keys**, use the [**global search bar**](../../get-started/the-stack.md#kibana-navigation-search). +1. To navigate to **API keys**, use the [**global search bar**](../../explore-analyze/find-and-organize/find-apps-and-objects.md). :::{image} ../../images/kibana-api-keys-search-bar.png :alt: api keys search bar diff --git a/solutions/security/advanced-entity-analytics/entity-store.md b/solutions/security/advanced-entity-analytics/entity-store.md index b1a7fdb28b..43cbfbf5dd 100644 --- a/solutions/security/advanced-entity-analytics/entity-store.md +++ b/solutions/security/advanced-entity-analytics/entity-store.md @@ -38,7 +38,7 @@ When the entity store is enabled, the following resources are generated for each To enable the entity store: -1. Find **Entity Store** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Entity Store** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. On the **Entity Store** page, turn the toggle on. Once you enable the entity store, the Entity Analytics dashboard displays the [**Entities**](../dashboards/entity-analytics-dashboard.md#entity-entities) section. @@ -57,5 +57,5 @@ Clearing entity store data permanently deletes persisted user and host records, To clear entity data: -1. Find **Entity Store** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Find **Entity Store** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. On the **Entity Store** page, select **Clear**. diff --git a/solutions/security/cloud/get-started-with-cwp-for-kubernetes.md b/solutions/security/cloud/get-started-with-cwp-for-kubernetes.md index 29e04caf50..fff1755209 100644 --- a/solutions/security/cloud/get-started-with-cwp-for-kubernetes.md +++ b/solutions/security/cloud/get-started-with-cwp-for-kubernetes.md @@ -24,7 +24,7 @@ This page describes how to set up Cloud Workload Protection (CWP) for Kubernetes First, you’ll need to deploy Elastic’s Defend for Containers integration to the Kubernetes clusters you wish to monitor. -1. Find **Container Workload Security** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Click **Add D4C Integration**. +1. Find **Container Workload Security** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Click **Add D4C Integration**. 2. Name the integration. The default name, which you can change, is `cloud_defend-1`. 3. Optional — make any desired changes to the integration’s policy by adjusting the **Selectors** and **Responses** sections. (For more information, refer to the [Defend for Containers policy guide](container-workload-protection-policies.md)). You can also change these later. 4. Under **Where to add this integration**, select an existing or new agent policy. @@ -54,7 +54,7 @@ In order to detect threats using this data, you’ll need active [detection rule To install and enable the prebuilt rules: -1. Find **Detection rules (SIEM)** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). Click **Add Elastic rules**. +1. Find **Detection rules (SIEM)** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Click **Add Elastic rules**. 2. Click the **Tags** filter next to the search bar, and search for the `Data Source: Elastic Defend for Containers` tag. 3. Select all the displayed rules, then click **Install *x* selected rule(s)**. 4. Return to the **Rules** page. Click the **Tags** filter next to the search bar, and search for the `Data Source: Elastic Defend for Containers` tag. @@ -72,7 +72,7 @@ To enable drift detection, you can use the default D4C policy: To enable drift prevention, create a new policy: -1. Find **Container Workload Security** in the navigation menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), then select your integration. +1. Find **Container Workload Security** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then select your integration. 2. Under **Selectors**, click **Add selector > File Selector**. By default, it selects the operations `createExecutable` and `modifyExecutable`. 3. Name the selector, for example: `blockDrift`. 4. Scroll down to the **Responses** section and click **Add response > File Response**. diff --git a/solutions/security/configure-elastic-defend/create-an-elastic-defend-policy-using-api.md b/solutions/security/configure-elastic-defend/create-an-elastic-defend-policy-using-api.md index dffaa4021c..a1fe7a86c5 100644 --- a/solutions/security/configure-elastic-defend/create-an-elastic-defend-policy-using-api.md +++ b/solutions/security/configure-elastic-defend/create-an-elastic-defend-policy-using-api.md @@ -79,7 +79,7 @@ Replace these values: 1. `` with your version of {{kib}}. 2. `` with the agent policy ID you received in step 1. -3. `` with the latest {{elastic-defend}} package version (for example, `8.9.1`). To find it, navigate to **Integrations** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), and select **{{elastic-defend}}**. +3. `` with the latest {{elastic-defend}} package version (for example, `8.9.1`). To find it, navigate to **Integrations** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), and select **{{elastic-defend}}**. This adds the {{elastic-defend}} integration to your agent policy with the default settings. @@ -488,7 +488,7 @@ Include the resulting JSON object in the following call to save your customized 1. `` with the {{elastic-defend}} policy ID you received in step 2. 2. `` with your version of {{kib}}. -3. `` with the latest {{elastic-defend}} package version (for example, `8.9.1`). To find it, navigate to **Integrations** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), and select **{{elastic-defend}}**. +3. `` with the latest {{elastic-defend}} package version (for example, `8.9.1`). To find it, navigate to **Integrations** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), and select **{{elastic-defend}}**. ```console curl --user : --request PUT \ diff --git a/solutions/security/detect-and-alert/cross-cluster-search-detection-rules.md b/solutions/security/detect-and-alert/cross-cluster-search-detection-rules.md index 140d683166..118adcb571 100644 --- a/solutions/security/detect-and-alert/cross-cluster-search-detection-rules.md +++ b/solutions/security/detect-and-alert/cross-cluster-search-detection-rules.md @@ -80,7 +80,7 @@ To update a rule’s API key, log into the local cluster as a user with the priv * Edit and save the rule. * Update the rule’s API key manually: - 1. Find **Stack Management** in the navigation menu or by using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), then go to **Rules**. + 1. Find **Stack Management** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then go to **Rules**. 2. Use the search box and filters to find the rules you want to update. For example, use the **Type** filter to find rules under the **Security** category. 3. Select the rule’s actions menu (**…​**), then **Update API key**. diff --git a/solutions/security/detect-and-alert/monitor-rule-executions.md b/solutions/security/detect-and-alert/monitor-rule-executions.md index 5f3c644af6..77dfe0c3b4 100644 --- a/solutions/security/detect-and-alert/monitor-rule-executions.md +++ b/solutions/security/detect-and-alert/monitor-rule-executions.md @@ -17,7 +17,7 @@ Refer to the [Troubleshoot missing alerts](../../../troubleshoot/security/detect ## Rule Monitoring tab [rule-monitoring-tab] -To view a summary of all rule executions, including the most recent failures and execution times, select the **Rule Monitoring** tab on the **Rules** page. To access the tab, find **Detection rules (SIEM)** in the navigation menu or look for “Detection rules (SIEM)” using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), then go to the **Rule Monitoring** tab. +To view a summary of all rule executions, including the most recent failures and execution times, select the **Rule Monitoring** tab on the **Rules** page. To access the tab, find **Detection rules (SIEM)** in the navigation menu or look for “Detection rules (SIEM)” using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then go to the **Rule Monitoring** tab. :::{image} ../../../images/security-monitor-table.png :alt: monitor table diff --git a/solutions/security/investigate/manage-integration.md b/solutions/security/investigate/manage-integration.md index 065959c816..939acbb8fe 100644 --- a/solutions/security/investigate/manage-integration.md +++ b/solutions/security/investigate/manage-integration.md @@ -35,7 +35,7 @@ Depending on your [subscription level](https://www.elastic.co/subscriptions), yo :::: -1. Go to **Fleet** using the navigation menu or the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), then open the **Agent policies** tab. +1. Go to **Fleet** using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then open the **Agent policies** tab. 2. Click the name of the agent policy where you want to adjust the Osquery configuration. The configuration changes you make only apply to the policy you select. 3. Click the name of the **Osquery Manager** integration, or add the integration first if the agent policy does not yet have it. 4. From the **Edit Osquery Manager integration** page, expand the **Advanced** section. @@ -101,7 +101,7 @@ If you encounter issues with **Osquery Manager**, find the relevant logs for {{e To get more details in the logs, change the agent logging level to debug: -1. Go to **Fleet** using the navigation menu or the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). +1. Go to **Fleet** using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Select the agent that you want to debug. 3. On the **Logs*** tab, change the ***Agent logging level*** to ***debug***, and then click ***Apply changes**. diff --git a/troubleshoot/security/agentless-integrations.md b/troubleshoot/security/agentless-integrations.md index 30d53c9675..324b2f63bc 100644 --- a/troubleshoot/security/agentless-integrations.md +++ b/troubleshoot/security/agentless-integrations.md @@ -20,7 +20,7 @@ For agentless integrations to successfully connect to {{elastic-sec}}, the {{fle To troubleshoot this issue: -1. Find **{{fleet}}** in the navigation menu or use the [global search field](../../get-started/the-stack.md#kibana-navigation-search). Go to the **Settings** tab. +1. Find **{{fleet}}** in the navigation menu or use the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md). Go to the **Settings** tab. 2. Under **{{fleet}} server hosts**, click the **Actions** button for the policy named `Default`. This opens the Edit {{fleet}} Server flyout. The policy named `Default` should have the **Make this {{fleet}} server the default one** setting enabled. If not, enable it, then delete your integration and create it again. ::::{note} @@ -52,7 +52,7 @@ Deleting your integration will remove all associated resources and stop data ing When you create a new agentless CSPM integration, a new agent policy appears within the **Agent policies** tab on the **{{fleet}}** page, but you can’t use the **Delete integration** button on this page. Instead, you must delete the integration from the CSPM Integration’s **Integration policies** tab. -1. Find **Integrations** in the navigation menu or use the [global search field](../../get-started/the-stack.md#kibana-navigation-search), then search for and select `CSPM`. +1. Find **Integrations** in the navigation menu or use the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md), then search for and select `CSPM`. 2. Go to the CSPM Integration’s **Integration policies** tab. 3. Find the integration policy for the integration you want to delete. Click **Actions**, then **Delete integration**. 4. Confirm by clicking **Delete integration** again.