Skip to content
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

Metrics: Measure synthetic source per-request document reconstruction latency #106659

Closed
salvatore-campagna opened this issue Mar 22, 2024 · 2 comments

Comments

@salvatore-campagna
Copy link
Contributor

salvatore-campagna commented Mar 22, 2024

Description

In the following months we will see usage of synthetic source increasing as a result of integrations adopting new index modes like tsdb and logs. When using synthetic source we reconstruct the original document using doc values and stored fields instead of just fetching the _source field. This implies larger latencies resulting from having to iterate all fields of a document to reconstruct the source instead of just fetching a single field. We would like to keep track of the time spent to reconstruct documents using synthetic source, measuring the per-request latency to reconstruct all the document sources involved in a specific request.

@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-storage-engine (Team:StorageEngine)

@salvatore-campagna salvatore-campagna changed the title [Monitoring] Measure synthetic source per-request document reconstruction latency [Metrics] Measure synthetic source per-request document reconstruction latency Mar 22, 2024
@salvatore-campagna salvatore-campagna changed the title [Metrics] Measure synthetic source per-request document reconstruction latency Metrics: Measure synthetic source per-request document reconstruction latency Mar 22, 2024
@salvatore-campagna salvatore-campagna self-assigned this Mar 22, 2024
@siposea siposea assigned lkts and unassigned salvatore-campagna Mar 25, 2024
@lkts
Copy link
Contributor

lkts commented May 22, 2024

#106732 is merged but we are missing a widget in a dashboard. As part of this work we also want to rename "TSDB" dashboard to "Storage engine" or similar.

@lkts lkts closed this as completed Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants