Is your feature request related to a problem? Please describe.
It's useful in experimentation and L2 escalations to understand what IO latencies pebble directly observes for reads that miss the block cache. The work under #85755 exports pebble observed fsync latencies, which is an improvement. This issue tracks also exporting read latencies.
Is your feature request related to a problem? Please describe.
It's useful in experimentation and L2 escalations to understand what IO latencies pebble directly observes for reads that miss the block cache. The work under #85755 exports pebble observed fsync latencies, which is an improvement. This issue tracks also exporting read latencies.
Jira issue: CRDB-20843
Epic CRDB-40360