Closed
Description
When synthetic source is enabled, it can be costly to retrieve the _source field, both in latency (we have to reconstruct the source) and S3 calls (in the case of Searchable Snapshots or Serverless data). It's possible there are Elastic components like Kibana Discover that are fetching _source when maybe they actually need specific fields, and so there might be a more efficient way to accomplish their goal.
Let's identify who is fetching _source where and why, so we can discuss alternatives. How is TBD but we could log accesses to source or implement specific telemetry or maybe use APM.