You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: solutions/observability/data-set-quality-monitoring.md
+3-6Lines changed: 3 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ products:
15
15
16
16
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.
17
17
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).
19
19
20
20
By default, the page only shows log data sets. To see other data set types, select them from the **Type** menu.
21
21
@@ -44,7 +44,7 @@ The Data Set Quality page provides several ways to help you investigate issues.
44
44
serverless: ga
45
45
```
46
46
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.
48
48
49
49
#### Required privileges
50
50
@@ -54,7 +54,6 @@ Accessing failure store requires the `read_failure_store` or `all` [index privil
54
54
55
55
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.
56
56
57
-
58
57
To understand how persistent an issue is, refer to **Document trends** for the number of failed documents over a selected time range:
59
58
60
59
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
64
63
65
64
1. From the data set table, select a data set name.
66
65
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.
68
67
69
68
### Find ignored fields in data sets [observability-monitor-datasets-find-ignored-fields-in-data-sets]
70
69
@@ -75,8 +74,6 @@ To open the details page for a data set with poor or degraded quality and view i
75
74
76
75
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).
77
76
78
-
% Screenshot
79
-
80
77
### Find ignored fields in individual logs [observability-monitor-datasets-find-ignored-fields-in-individual-logs]
81
78
82
79
To use Discover to find ignored fields in individual logs:
0 commit comments