[Observability] New solution navigation for 9.2

solutions/observability/apm/control-access-to-apm-data.md

@@ -223,7 +223,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](/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`.
+Next, you’ll need to create a {{kib}} space for each service environment. Open **Spaces** from the navigation menu or using 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.
 
@@ -242,7 +242,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](/explore-analyze/find-and-organize/find-apps-and-objects.md). Click **Create role**.
+Open **Roles** from the navigation menu or using 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`).
 

solutions/observability/apm/cross-cluster-search.md

@@ -33,7 +33,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](/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 the Applications UI — Find **Applications** in the navigation 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`](/deploy-manage/stack-settings.md) — Update the [`xpack.apm.indices.*`](kibana://reference/configuration-reference/apm-settings.md) configuration values to include remote clusters.
 
 ::::{tip}
@@ -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](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. To open **Advanced settings**, find it in the navigation 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.
 
 ::::

solutions/observability/apm/custom-filters.md

@@ -74,7 +74,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/docs/api/doc/elasticsearch/group/endpoint-ingest), 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).
+This tutorial uses the [Ingest APIs](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-ingest), but it’s also possible to create a pipeline using the UI. Open  **Ingest Pipelines** in the navigation menu or using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then click **Create pipeline** → **New pipeline**.
 ::::
 
 To start, create a pipeline with a simple description and an empty array of processors:

solutions/observability/apm/data-streams.md

@@ -87,7 +87,7 @@ For example, consider traces that would originally be indexed to `traces-apm-def
 ]
 ```
 
-To find other ingest pipelines from the {{es}} apm-data plugin that are called by default, go to **Stack management** → **Ingest pipelines** [in Kibana](/deploy-manage/index.md) and search for `apm`. Default APM ingest pipelines will follow the pattern `*-apm*@default-pipeline`.
+To find other ingest pipelines from the {{es}} apm-data plugin that are called by default, go to **Ingest pipelines** in the navigation menu or using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), and search for `apm`. Default APM ingest pipelines will follow the pattern `*-apm*@default-pipeline`.
 
 For more custom APM ingest pipeline guides, see [parse data using ingest pipelines](/solutions/observability/apm/parse-data-using-ingest-pipelines.md).
 

solutions/observability/apm/grant-access-using-api-keys.md

@@ -22,7 +22,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](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. Open **API keys** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
 2. Click **Create API key**.
 
     :::{image} /solutions/images/observability-server-api-key-create.png
@@ -94,7 +94,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](/explore-analyze/find-and-organize/find-apps-and-objects.md). Click **Create API key**.
+To open **API keys**, find it in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Click **Create API key**.
 
 :::{image} /solutions/images/observability-server-api-key-create.png
 :alt: API key creation

solutions/observability/apm/index-lifecycle-management.md

@@ -63,7 +63,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](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. Open **Index Management** from the navigation menu or using 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.
@@ -75,7 +75,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](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. Open **Lifecycle Policies** from the navigation menu or using 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**.

solutions/observability/apm/logs.md

@@ -35,7 +35,7 @@ Logs displayed on this page are filtered on `service.name`
 stack: preview 9.0
 ```
 
-For an enhanced logs view with additional information including the log pattern, the number of events for each log, change type, and the time the change occurred, turn on the `observability:newLogsOverview` setting in **Management** → **Stack Management** → **Advanced Settings**.
+For an enhanced logs view with additional information including the log pattern, the number of events for each log, change type, and the time the change occurred, turn on the `observability:newLogsOverview` [advanced setting](kibana://reference/advanced-settings.md#kibana-search-settings).
 
 ## Integrate with logging frameworks [apm-logs-correlation]
 ```{applies_to}

solutions/observability/apm/reduce-storage.md

@@ -77,7 +77,7 @@ POST /.ds-*-apm*/_delete_by_query
 
 {{kib}}'s [Index management](/manage-data/data-store/index-basics.md#index-management) UI 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](/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**.
+Open **Index Management** in the navigation menu or using 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]
 

solutions/observability/apm/view-elasticsearch-index-template.md

@@ -12,7 +12,7 @@ products:
 
 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](/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.
+The default APM index templates can be viewed in {{kib}}. To open **Index Management**, find it 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]
 
@@ -22,7 +22,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](/solutions/observability/apm/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**.
+First, determine which [data stream](/solutions/observability/apm/data-streams.md) you’d like to edit in {{kib}}. To open **Index Management**, find it in the navigation 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: `<name_of_data_stream>@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**.
 

solutions/observability/cloud/monitor-aws-network-firewall-logs.md

@@ -39,7 +39,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](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. Find **Integrations** in the navigation 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**.
 
@@ -76,7 +76,7 @@ Creating a Network Firewall is not trivial and is beyond the scope of this guide
 
         1. Go to the [Elastic Cloud](https://cloud.elastic.co/) console
         2. Select **Open Kibana**.
-        3. Expand the left-hand menu, under **Management** select **Stack management > API Keys** and click **Create API key**. If you are using an API key with **Restrict privileges**, make sure to review the Indices privileges to provide at least `auto_configure` and `write` permissions for the indices you will be using with this delivery stream.
+        3. Open **API keys** in the navigation menu or using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then click **Create API key**. If you are using an API key with **Restrict privileges**, make sure to review the Indices privileges to provide at least `auto_configure` and `write` permissions for the indices you will be using with this delivery stream.
 
 4. Set up the delivery stream by specifying the following data:
 

solutions/observability/cloud/monitor-cloudtrail-logs.md

@@ -102,7 +102,7 @@ You now have a CloudWatch log group with events coming from CloudTrail. For more
 
         1. Go to the [Elastic Cloud](https://cloud.elastic.co/) console
         2. Select **Open Kibana**.
-        3. Expand the left-hand menu, under **Management** select **Stack management > API Keys** and click **Create API key**. If you are using an API key with **Restrict privileges**, make sure to review the Indices privileges to provide at least `auto_configure` and `write` permissions for the indices you will be using with this delivery stream.
+        3. Open **API keys** in the navigation menu or using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then click **Create API key**. If you are using an API key with **Restrict privileges**, make sure to review the Indices privileges to provide at least `auto_configure` and `write` permissions for the indices you will be using with this delivery stream.
 
 2. Set up the delivery stream by specifying the following data:
 

solutions/observability/cloud/monitor-cloudwatch-logs.md

@@ -125,7 +125,7 @@ Take note of the log group name for this Lambda function, as you will need it in
 
         1. Go to the [Elastic Cloud](https://cloud.elastic.co/) console
         2. Select **Open Kibana**.
-        3. Expand the left-hand menu, under **Management** select **Stack management > API Keys** and click **Create API key**. If you are using an API key with **Restrict privileges**, make sure to review the Indices privileges to provide at least `auto_configure` and `write` permissions for the indices you will be using with this delivery stream.
+        3. Open **API keys** in the navigation menu or using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then click **Create API key**.If you are using an API key with **Restrict privileges**, make sure to review the Indices privileges to provide at least `auto_configure` and `write` permissions for the indices you will be using with this delivery stream.
 
     * **Content encoding**: To reduce the data transfer costs, use GZIP encoding.
     * **Retry duration**: Determines how long Firehose continues retrying the request in the event of an error. A duration between 60 and 300 seconds should be suitable for most use cases.

solutions/observability/cloud/monitor-web-application-firewall-waf-logs.md

@@ -71,7 +71,7 @@ For advanced use cases, source records can be transformed by invoking a custom L
 
         1. Go to the [Elastic Cloud](https://cloud.elastic.co/) console
         2. Select **Open Kibana**.
-        3. Expand the left-hand menu, under **Management** select **Stack management > API Keys** and click **Create API key**. If you are using an API key with **Restrict privileges**, make sure to review the Indices privileges to provide at least `auto_configure` and `write` permissions for the indices you will be using with this delivery stream.
+        3. Open **API keys** in the navigation menu or using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then click **Create API key**. If you are using an API key with **Restrict privileges**, make sure to review the Indices privileges to provide at least `auto_configure` and `write` permissions for the indices you will be using with this delivery stream.
 
     * **Content encoding**: For a better network efficiency, leave content encoding set to GZIP.
     * **Retry duration**: Determines how long Firehose continues retrying the request in the event of an error. A duration of 60-300s should be suitable for most use cases.

solutions/observability/data-set-quality-monitoring.md

@@ -15,7 +15,7 @@ products:
 
 The **Data Set Quality** page provides an overview of your log, metric, trace, and synthetic data sets. You can then use this information to get an idea of your overall data set quality and find data sets that contain incorrectly parsed documents.
 
-To open the **Data Set Quality** page, find it under **Stack Management** in the main menu, or search for "data set quality" using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+To open the **Data Set Quality** management page, find it in the navigation menu or by using 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.
 

solutions/observability/incident-management/configure-service-level-objective-slo-access.md

@@ -33,7 +33,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](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. Open the **Roles** management page by finding it in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
 2. On the **Roles** page, click **Create role**.
 
 

solutions/observability/incident-management/create-a-degraded-docs-rule.md

@@ -32,7 +32,7 @@ To access this rule from the **Alerts** page:
 
 You can also access this rule from the **Data Set Quality** page:
 
-1. Go to **Stack Management** → **Data Set Quality** or search for "Data Set Quality" using the [global search field](../../../explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. To open **Data Set Quality**, find it in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
 1. Select a data set name from the data set table.
 1. Select **Actions** in the upper-right corner of the page.
 1. Select **Create rule**.

solutions/observability/incident-management/create-log-threshold-rule.md

@@ -337,7 +337,7 @@ When a rule check is performed, a query is built based on the configuration of t
 
 ## Settings [settings]
 
-With log threshold rules, it’s not possible to set an explicit index pattern as part of the configuration. The index pattern is instead inferred from **Log sources** at **Stack Management** → **Advanced settings** under **Observability**.
+With log threshold rules, it’s not possible to set an explicit index pattern as part of the configuration. The index pattern is instead inferred from the **Log sources** [advanced setting](kibana://reference/advanced-settings.md#kibana-search-settings).
 
 With each execution of the rule check, the **Log indices** setting is checked, but it is not stored when the rule is created.
 

solutions/observability/infra-and-hosts/analyze-compare-hosts.md

@@ -123,7 +123,7 @@ To see logs for a specific host, refer to [View host details](/solutions/observa
 stack: preview 9.0
 ```
 
-For an enhanced logs view with additional information including the log pattern, the number of events for each log, change type, and the time the change occurred, turn on the `observability:newLogsOverview` setting in **Management** → **Stack Management** → **Advanced Settings**.
+For an enhanced logs view with additional information including the log pattern, the number of events for each log, change type, and the time the change occurred, turn on the `observability:newLogsOverview` [advanced setting](kibana://reference/advanced-settings.md#kibana-search-settings).
 
 
 ## View alerts [analyze-hosts-view-alerts]