-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Dataset quality] Added malformed docs column to table #172462
Conversation
Pinging @elastic/apm-ui (Team:APM) |
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
Pinging @elastic/obs-ux-logs-team (Team:obs-ux-logs) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
x-pack/plugins/dataset_quality/common/data_streams_stats/malformed_docs_stat.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/dataset_quality/public/utils/default_timerange.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/dataset_quality/public/components/dataset_quality/columns.tsx
Outdated
Show resolved
Hide resolved
x-pack/plugins/dataset_quality/public/components/quality_indicator/indicator.tsx
Outdated
Show resolved
Hide resolved
…e different from the number of malformed documents
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management) |
.get<GetDataStreamsStatsResponse>(DATA_STREAMS_STATS_URL, { | ||
query: params, | ||
}) | ||
.catch((error) => { | ||
throw new GetDataStreamsStatsError(`Failed to fetch data streams stats": ${error}`); | ||
}); | ||
|
||
const { dataStreamsStats, integrations } = decodeOrThrow( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TIL that we have this helper function 👍🏼
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's awesome, from what I saw it was created in the shared repo by @weltenwort 🎉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Glad it's useful. It also formats the error in a more helpful way than the default formatter (IMO).
x-pack/plugins/dataset_quality/public/services/data_streams_stats/data_streams_stats_client.ts
Show resolved
Hide resolved
|
||
const datasetQualityESClient = createDatasetQualityESClient(esClient); | ||
|
||
const response = await datasetQualityESClient.search({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for future: I think it would be a great idea to add some latency telemetry for this query.
x-pack/plugins/dataset_quality/server/routes/data_streams/routes.ts
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍🏼
/oblt-deploy |
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]Module Count
Public APIs missing exports
Page load bundle
History
To update your PR or re-run it, just comment with: |
Let's not call them "Malformed docs" as that would indicate that the reason for the fields being in Suggestions for alternatives:
Also, note that since elastic/elasticsearch#101373 hasn't been merged yet, the |
@felixbarny we have this little tooltip helper ![]() would that help reducing the confusion there?
what do you think about the suggestions @mdbirnstiehl and @ruflin? what would be the most clear one?
Can we do something in the meantime? I expected the query to be expensive and that's why also @weltenwort suggested not to sort by that column by default, since that would put it in the critical path for loading the table. |
That would be my preference as it always applies to the failure store. Document is degraded because some processing didn't happen.
I would just ignore it for now and keep it expensive. |
Renamed to |
Not sure I fully understand. We should call documents in the failure store "failed documents" and documents that are in the regular data stream but have an |
What do you call it if you need to "munch" both into a single statistic? :-) Maybe the solution is just to have both. At the same time I would like to be able to have a "summary" of being able to tell the state of the dataset. |
I guess I'd call it health then. |
Health unfortunately is already used for shards / replicas of data streams ... |
Ingestion health? |
How about "consistency", "integrity", or "quality"? |
Closes #170220.
Changes
GET /internal/dataset_quality/data_streams/malformed_docs
data_streams_stats_client.ts
as suggested by @tonyghiani in [Dataset quality] Implementing Dataset Table + consuming plugin from observability log explorer #171777._ignored
properties.columns.tsx
.Demo
Screen.Recording.2023-12-04.at.13.18.08.mov
How to test?
Malformed docs
column should be present and should be sortable