We've received feedback to not only surface average latency but also the Max, P99, P90, P50, and Min latencies for a given fingerprint in each aggregation interval. We surface the standard deviation but the user reported that it was an indirect way to detect outliers.

Ideally they'd like to be able to view our P99 latency time-series metrics (or any other P90 metric), go to the statements overview page at the time period (with persisted stats), sort by P99 latency, and identify the statement fingerprint to troubleshoot.

From there, they'd be able to view fingerprint details (execution statistics, unique plans, contention information, outlier execution details, etc.)

Jira issue: CRDB-11358

Epic CRDB-32139