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
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.
The text was updated successfully, but these errors were encountered:
#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.
Description
In the following months we will see usage of synthetic source increasing as a result of integrations adopting new index modes like
tsdb
andlogs
. 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.The text was updated successfully, but these errors were encountered: