diff --git a/docs/en/observability/images/data-set-quality-overview.png b/docs/en/observability/images/data-set-quality-overview.png
new file mode 100644
index 0000000000..1673d3b56c
Binary files /dev/null and b/docs/en/observability/images/data-set-quality-overview.png differ
diff --git a/docs/en/observability/images/logs-dataset-overview.png b/docs/en/observability/images/logs-dataset-overview.png
deleted file mode 100644
index 0676e3aac0..0000000000
Binary files a/docs/en/observability/images/logs-dataset-overview.png and /dev/null differ
diff --git a/docs/en/observability/index.asciidoc b/docs/en/observability/index.asciidoc
index f8e3dab042..c6fe11ddb1 100644
--- a/docs/en/observability/index.asciidoc
+++ b/docs/en/observability/index.asciidoc
@@ -194,8 +194,6 @@ include::inspect-log-anomalies.asciidoc[leveloffset=+3]
 
 include::configure-logs-sources.asciidoc[leveloffset=+3]
 
-include::logs-monitor-datasets.asciidoc[leveloffset=+2]
-
 include::logs-add-service-name.asciidoc[leveloffset=+2]
 
 include::logs-index-template.asciidoc[leveloffset=+2]
@@ -235,6 +233,9 @@ include::slo-privileges.asciidoc[leveloffset=+3]
 
 include::slo-create.asciidoc[leveloffset=+3]
 
+//Data Set Quality
+include::logs-monitor-datasets.asciidoc[leveloffset=+1]
+
 //Observability AI Assistant
 include::observability-ai-assistant.asciidoc[leveloffset=+1]
 
diff --git a/docs/en/observability/logs-monitor-datasets.asciidoc b/docs/en/observability/logs-monitor-datasets.asciidoc
index 329cb25282..a3494c68bb 100644
--- a/docs/en/observability/logs-monitor-datasets.asciidoc
+++ b/docs/en/observability/logs-monitor-datasets.asciidoc
@@ -1,14 +1,16 @@
 [[monitor-datasets]]
-= Monitor log data set quality
+= Data set quality
 
 beta:[]
 
-The **Data Set Quality** page provides an overview of your log data sets.
-Use this information to get an idea of your overall log data set quality and find data sets that contain incorrectly parsed documents.
+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.
+
 Access the Data Set Quality page from the main {kib} menu at **Stack Management** → **Data Set Quality**.
+By default, the page only shows log data sets. To see other data set types, select them from the **Type** menu.
 
 [role="screenshot"]
-image::images/logs-dataset-overview.png[Screen capture of the data set overview]
+image::images/data-set-quality-overview.png[Screen capture of the data set overview]
 
 .Requirements
 [NOTE]
@@ -36,7 +38,7 @@ Opening the details of a specific data set shows the degraded documents history,
 
 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.
-You can also open a data set in Logs Explorer to find ignored fields in individual logs.
+Open a logs data set in Logs Explorer or other data set types in Discover to find ignored fields in individual documents.
 
 [discrete]
 [[find-ignored-fields-in-data-sets]]
@@ -51,19 +53,19 @@ The **Quality issues** section shows fields that were ignored during ingest, the
 
 [discrete]
 [[find-ignored-fields-in-individual-logs]]
-=== Find ignored fields in individual logs
+=== Find ignored fields in individual documents
 
-To use Logs Explorer to find ignored fields in individual logs:
+To use Logs Explorer or Discover to find ignored fields in individual documents:
 
 . Find data sets with degraded documents using the **Degraded Docs** column of the data sets table.
-. Click the percentage in the **Degraded Docs** column to open the data set in Logs Explorer.
+. Click the percentage in the **Degraded Docs** column to open the data set in Logs Explorer or Discover.
 
-The **Documents** table in Logs Explorer is automatically filtered to show documents that were not parsed correctly.
+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.
 
 Now that you know which documents contain ignored fields, examine them more closely to find the origin of the issue:
 
-. Under the **actions** column, click image:images/expand-icon.png[expand icon] to open the log details.
+. Under the **actions** column, click image:images/expand-icon.png[expand icon] to open the document details.
 . Select the **JSON** tab.
 . Scroll towards the end of the JSON to find the `ignored_field_values`.