elastic · mdbirnstiehl · Apr 7, 2025 · Mar 5, 2025 · Mar 5, 2025 · Mar 6, 2025
diff --git a/redirects.yml b/redirects.yml
@@ -3,4 +3,5 @@ redirects:
   'deploy-manage/security/manually-configure-security-in-self-managed-cluster.md': '!deploy-manage/security/self-setup.md'
   'deploy-manage/security/security-certificates-keys.md': '!deploy-manage/security/self-auto-setup.md'
   'deploy-manage/security/ece-traffic-filtering-through-the-api.md': 'deploy-manage/security/ec-traffic-filtering-through-the-api.md'
-  'deploy-manage/security/install-stack-demo-secure.md': '!deploy-manage/security/self-setup.md'
+  'deploy-manage/security/install-stack-demo-secure.md': '!deploy-manage/security/self-setup.md'
+  'reference/observability/fields-and-object-schemas/logs-app-fields.md': '!reference/observability/fields-and-object-schemas.md'
diff --git a/reference/fleet/monitor-elastic-agent.md b/reference/fleet/monitor-elastic-agent.md
@@ -135,7 +135,6 @@ On the **Logs** tab you can filter, search, and explore the agent logs:
 
 * Change the log level to filter the view by log levels. Want to see debugging logs? Refer to [Change the logging level](#change-logging-level).
 * Change the time range to view historical logs.
-* Click **Open in Logs** to tail agent log files in real time. For more information about logging, refer to [Tail log files](/solutions/observability/logs/logs-stream.md).
 
 
 ## Change the logging level [change-logging-level]

diff --git a/reference/observability/fields-and-object-schemas.md b/reference/observability/fields-and-object-schemas.md
@@ -5,16 +5,13 @@ mapped_pages:
 
 # Fields and object schemas [fields-reference]
 
-This section lists Elastic Common Schema (ECS) fields the Logs and Infrastructure apps use to display data.
+This section lists Elastic Common Schema (ECS) fields the Infrastructure apps use to display data.
 
 ECS is an open source specification that defines a standard set of fields to use when storing event data in {{es}}, such as logs and metrics.
 
-Beat modules (for example, [{{filebeat}} modules](beats://reference/filebeat/filebeat-modules.md)) are ECS-compliant, so manual field mapping is not required, and all data is populated automatically in the Logs and Infrastructure apps. If you cannot use {{beats}}, map your data to [ECS fields](ecs://reference/ecs-converting.md)). You can also try using the experimental [ECS Mapper](https://github.com/elastic/ecs-mapper) tool.
+Beat modules (for example, [{{filebeat}} modules](beats://reference/filebeat/filebeat-modules.md)) are ECS-compliant, so manual field mapping is not required, and all data is populated automatically in the Infrastructure app. If you cannot use {{beats}}, map your data to [ECS fields](ecs://reference/ecs-converting.md)). You can also try using the experimental [ECS Mapper](https://github.com/elastic/ecs-mapper) tool.
 
-This reference covers:
-
-* [Logs Explorer fields](/reference/observability/fields-and-object-schemas/logs-app-fields.md)
-* [{{infrastructure-app}} fields](/reference/observability/fields-and-object-schemas/metrics-app-fields.md)
+This reference covers [{{infrastructure-app}} fields](/reference/observability/fields-and-object-schemas/metrics-app-fields.md).
 
 
 
diff --git a/reference/observability/fields-and-object-schemas/logs-app-fields.md b/reference/observability/fields-and-object-schemas/logs-app-fields.md
diff --git a/reference/observability/index.md b/reference/observability/index.md
@@ -13,7 +13,7 @@ mapped_pages:
 This section contains reference information for Elastic Observability features, including:
 
 * Fields reference
-  * Logs Explorer fields
+  * Logs Discover fields
   * Infrastructure app fields
 * Elastic Entity Model
 

diff --git a/reference/observability/toc.yml b/reference/observability/toc.yml
@@ -2,7 +2,6 @@ toc:
   - file: index.md
   - file: fields-and-object-schemas.md
     children:
-      - file: fields-and-object-schemas/logs-app-fields.md
       - file: fields-and-object-schemas/metrics-app-fields.md
   - file: elastic-entity-model.md
   - file: serverless/infrastructure-app-fields.md
diff --git a/solutions/images/logs-discover.png b/solutions/images/logs-discover.png
diff --git a/solutions/observability.md b/solutions/observability.md
@@ -25,7 +25,7 @@ applies_to:
 
 ## How to [_how_to]
 
-* [**Explore log data**](observability/logs/logs-explorer.md): Use Discover to explore your log data.
+* [**Explore log data**](observability/logs/discover-logs.md): Use Discover to explore your log data.
 * [**Trigger alerts and triage problems**](../solutions/observability/incident-management/create-manage-rules.md): Create rules to detect complex conditions and trigger alerts.
 * [**Track and deliver on your SLOs**](observability/incident-management/service-level-objectives-slos.md): Measure key metrics important to the business.
 * [**Detect anomalies and spikes**](../explore-analyze/machine-learning/anomaly-detection.md): Find unusual behavior in time series data.

diff --git a/solutions/observability/apps/collect-metrics.md b/solutions/observability/apps/collect-metrics.md
@@ -38,7 +38,7 @@ See the [Open Telemetry Metrics API](https://github.com/open-telemetry/opentelem
 Use **Discover** to validate that metrics are successfully reported to {{kib}}.
 
 1. Open your Observability instance.
-2. Find **Discover** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search), and select the **Logs Explorer** tab.
+2. Find **Discover** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search).
 3. Click **All logs** → **Data Views** then select **APM**.
 4. Filter the data to only show documents with metrics: `processor.name :"metric"`
 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/solutions/observability/cloud/monitor-cloudtrail-logs.md b/solutions/observability/cloud/monitor-cloudtrail-logs.md
@@ -209,11 +209,6 @@ Navigate to {{kib}} and choose among the following monitoring options:
     :alt: Visualize CloudTrail logs with Disocver
     :::
 
-* **Visualize your logs with Logs explorer**
-
-    :::{image} /solutions/images/observability-firehose-cloudtrail-logsexplorer.png
-    :alt: Visualize CloudTrail logs with Logs explorer
-    :::
 
 * **Visualize your logs with the CloudTrail Dashboard**
 

diff --git a/solutions/observability/cloud/monitor-microsoft-azure-openai.md b/solutions/observability/cloud/monitor-microsoft-azure-openai.md
@@ -246,7 +246,6 @@ Now that your log and metric data is streaming to {{es}}, you can view them in {
 
 * [View logs and metrics with the overview dashboard](#azure-openai-overview-dashboard): Use the built-in overview dashboard for insight into your Azure OpenAI service like total requests and token usage.
 * [View logs and metrics with Discover](#azure-openai-discover): Use Discover to find and filter your log and metric data based on specific fields.
-* [View logs with Logs Explorer](#azure-openai-logs-explorer): Use Logs Explorer for an in-depth view into your logs.
 
 
 ### View logs and metrics with the overview dashboard [azure-openai-overview-dashboard]
@@ -279,28 +278,6 @@ From here, filter your data and dive deeper into individual logs to find informa
 
 For more on using Discover and creating data views, refer to the [Discover](../../../explore-analyze/discover.md) documentation.
 
-
-### 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](/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} /solutions/images/observability-log-explorer.png
-:alt: screenshot of the logs explorer main page
-:screenshot:
-:::
-
-From **Logs Explorer**, you can select the Azure OpenAI integration from the data selector to view your Kubernetes data.
-
-![screenshot of the logs explorer data selector](/solutions/images/observability-azure-open-ai-data-selector.png "")
-
-From here, filter your log data and dive deeper into individual logs to find information and troubleshoot issues. For a list of Azure OpenAI fields you may want to filter by, refer to the [Azure OpenAI integration](https://docs.elastic.co/en/integrations/azure_openai#settings) documentation.
-
-For more on Logs Explorer, refer to:
-
-* [Logs Explorer](../logs/logs-explorer.md) for an overview of Logs Explorer.
-* [Filter logs in Logs Explorer](../logs/filter-aggregate-logs.md#logs-filter-logs-explorer) for more on filtering logs in Logs Explorer.
-
-
 ## Step 6: Monitor Microsoft Azure OpenAI APM with OpenTelemetry [azure-openai-apm]
 
 The Azure OpenAI API provides useful data to help monitor and understand your code. Using OpenTelemetry, you can ingest this data into Elastic {{observability}}. From there, you can view and analyze your data to monitor the cost and performance of your applications.

diff --git a/...ns/observability/cloud/monitor-microsoft-azure-with-azure-native-isv-service.md b/...ns/observability/cloud/monitor-microsoft-azure-with-azure-native-isv-service.md
@@ -98,7 +98,7 @@ To ingest Azure subscription and resource logs into Elastic, you use the Azure N
     ::::
 
 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**.
+4. To analyze your subscription and resource logs, click **Show Logs**.
 
 
 ## Step 3: Ingest logs and metrics from your virtual machines (VMs) [azure-ingest-VM-logs-metrics]
@@ -112,7 +112,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"`.
+4. Back in {{kib}}, view the **Discover** 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](/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
@@ -91,7 +91,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](/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**.
+4. To analyze your subscription and resource logs, click **Show Logs**.
 
 
 ## Step 3: Ingest logs and metrics from your virtual machines. [azure-step-three]
@@ -104,7 +104,7 @@ To ingest Azure subscription and resource logs into Elastic using the Microsoft
 
     ![Select VMs to collect logs and metrics from](/solutions/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](/explore-analyze/find-and-organize/find-apps-and-objects.md)).
+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 **Discover** (find `Discover` 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](/explore-analyze/find-and-organize/find-apps-and-objects.md).)
 

diff --git a/solutions/observability/data-set-quality-monitoring.md b/solutions/observability/data-set-quality-monitoring.md
@@ -2,10 +2,10 @@
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/monitor-datasets.html
   - https://www.elastic.co/guide/en/serverless/current/observability-monitor-datasets.html
+navigation_title: "Data set quality"
 applies_to:
   stack: beta
   serverless: beta
-navigation_title: "Data set quality"
 ---
 
 # Data set quality monitoring [observability-monitor-datasets]
@@ -35,7 +35,7 @@ Opening the details of a specific data set shows the degraded documents history,
 
 ## Investigate issues [observability-monitor-datasets-investigate-issues]
 
-The Data Set Quality page has a couple of different ways to help you find ignored fields and investigate issues. From the data set table, you can open the data set’s details page, and view commonly ignored fields and information about those fields. Open a logs data set in Logs Explorer or other data set types in Discover to find ignored fields in individual documents.
+The Data Set Quality page has a couple of different ways to help you find ignored fields and investigate issues. From the data set table, you can open the data set’s details page, and view commonly ignored fields and information about those fields. Open a logs data set in Discover or other data set types in Discover to find ignored fields in individual documents.
 
 
 ### Find ignored fields in data sets [observability-monitor-datasets-find-ignored-fields-in-data-sets]
@@ -50,12 +50,12 @@ The **Quality issues** section shows fields that have been ignored, the number o
 
 ### Find ignored fields in individual logs [observability-monitor-datasets-find-ignored-fields-in-individual-logs]
 
-To use Logs Explorer or Discover to find ignored fields in individual logs:
+To use Discover to find ignored fields in individual logs:
 
 1. Find data sets with degraded documents using the **Degraded Docs** column of the data sets table.
-2. Click the percentage in the **Degraded Docs** column to open the data set in Logs Explorer or Discover.
+2. Click the percentage in the **Degraded Docs** column to open the data set in Discover.
 
-The **Documents** table in Logs Explorer or Discover is automatically filtered to show documents that were not parsed correctly. Under the **actions** column, you’ll find the degraded document icon (![degraded document icon](/solutions/images/serverless-indexClose.svg "")).
+The **Documents** table in Discover is automatically filtered to show documents that were not parsed correctly. Under the **actions** column, you’ll find the degraded document icon (![degraded document icon](../images/serverless-indexClose.svg "")).
 
 Now that you know which documents contain ignored fields, examine them more closely to find the origin of the issue:
 

diff --git a/solutions/observability/get-started/quickstart-monitor-hosts-with-elastic-agent.md b/solutions/observability/get-started/quickstart-monitor-hosts-with-elastic-agent.md
@@ -134,7 +134,7 @@ After installation is complete and all relevant data is flowing into Elastic, th
 | Integration asset | Description |
 | --- | --- |
 | **Apache** | Prebuilt dashboard for monitoring Apache HTTP server health using error and access log data. |
-| **Custom .log files** | Logs Explorer for analyzing custom logs. |
+| **Custom .log files** | Discover for analyzing custom logs. |
 | **Docker** | Prebuilt dashboard for monitoring the status and health of Docker containers. |
 | **MySQL** | Prebuilt dashboard for monitoring MySQl server health using error and access log data. |
 | **Nginx** | Prebuilt dashboard for monitoring Nginx server health using error and access log data. |
@@ -160,7 +160,7 @@ For host monitoring, the following capabilities and features are recommended:
     * [Detect anomalies](../../../solutions/observability/infra-and-hosts/detect-metric-anomalies.md) for memory usage and network traffic on hosts.
     * [Create alerts](../../../solutions/observability/incident-management/alerting.md) that notify you when an anomaly is detected or a metric exceeds a given value.
 
-* In the [Logs Explorer](../../../solutions/observability/logs/logs-explorer.md), search and filter your log data, get information about the structure of log fields, and display your findings in a visualization. You can also:
+* In [Discover](../../../solutions/observability/logs/discover-logs.md), search and filter your log data, get information about the structure of log fields, and display your findings in a visualization. You can also:
 
     * [Monitor log data set quality](../../../solutions/observability/data-set-quality-monitoring.md) to find degraded documents.
     * [Run a pattern analysis](../../../explore-analyze/machine-learning/machine-learning-in-kibana/xpack-ml-aiops.md#log-pattern-analysis) to find patterns in unstructured log messages.