Skip to content

Commit 7725e8d

Browse files
committed
review changes
1 parent c5c21a8 commit 7725e8d

File tree

1 file changed

+3
-6
lines changed

1 file changed

+3
-6
lines changed

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

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ products:
1515

1616
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.
1717

18-
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).
18+
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).
1919

2020
By default, the page only shows log data sets. To see other data set types, select them from the **Type** menu.
2121

@@ -44,7 +44,7 @@ The Data Set Quality page provides several ways to help you investigate issues.
4444
serverless: ga
4545
```
4646

47-
To help diagnose issues with ingestion or mapping, documents that are rejected during ingestion are sent to a dedicated data stream called failure store. From the **Data Set Quality** page, data streams with documents in the failure store will show a percentage in the **Failed docs (%)** column. The failed docs percentage gives you a quick look at the magnitude of potential problems in your ingestion process.
47+
To help diagnose issues with ingestion or mapping, documents that are rejected during ingestion are sent to a dedicated data stream called failure store. On the **Data Set Quality** page, data streams with documents in the failure store will show a percentage in the **Failed docs (%)** column. The failed docs percentage gives you a quick look at the magnitude of potential problems in your ingestion process.
4848

4949
#### Required privileges
5050

@@ -54,7 +54,6 @@ Accessing failure store requires the `read_failure_store` or `all` [index privil
5454

5555
Select the percentage in the **Failed docs (%)** column for a specific data stream to open Discover and see the raw documents that were sent to failure store.
5656

57-
5857
To understand how persistent an issue is, refer to **Document trends** for the number of failed documents over a selected time range:
5958

6059
1. Select the data set name from the main table.
@@ -64,7 +63,7 @@ To help diagnose what's causing an issue, refer to **Quality issues** for error
6463

6564
1. From the data set table, select a data set name.
6665
1. Scroll down to **Quality issues**.
67-
1. Click the expand icon to open a summary of why
66+
1. Click the expand icon to open a summary of why your document failed.
6867

6968
### Find ignored fields in data sets [observability-monitor-datasets-find-ignored-fields-in-data-sets]
7069

@@ -75,8 +74,6 @@ To open the details page for a data set with poor or degraded quality and view i
7574

7675
The **Quality issues** section shows fields that have been ignored, the number of documents that contain ignored fields, the timestamp of last occurrence of the field being ignored, and failed documents (serverless only).
7776

78-
% Screenshot
79-
8077
### Find ignored fields in individual logs [observability-monitor-datasets-find-ignored-fields-in-individual-logs]
8178

8279
To use Discover to find ignored fields in individual logs:

0 commit comments

Comments
 (0)