diff --git a/docs/generated/sql/functions.md b/docs/generated/sql/functions.md index 786a1b16fa62..859ccc8e84de 100644 --- a/docs/generated/sql/functions.md +++ b/docs/generated/sql/functions.md @@ -3101,6 +3101,25 @@ table. Returns an error if validation fails.
Function → Returns | Description |
---|---|
crdb_internal.probe_ranges(timeout: interval, probe_type: unknown_enum) → tuple{int AS range_id, string AS error, int AS end_to_end_latency_ms, string AS verbose_trace} | Returns rows of range data based on the results received when using the prober. +Parameters +timeout: interval for the maximum time the user wishes the prober to probe a range. +probe_type: enum indicating which kind of probe the prober should conduct (options are read or write). +Example usage +number of failed write probes: select count(1) from crdb_internal.probe_ranges(INTERVAL ‘1000ms’, ‘write’) where error != ‘’; +50 slowest probes: select range_id, error, end_to_end_latency_ms from crdb_internal.probe_ranges(INTERVAL ‘1000ms’, true) order by end_to_end_latency_ms desc limit 50; +Notes +If a probe should fail, the latency will be set to MaxInt64 in order to naturally sort above other latencies. +Read probes are cheaper than write probes. If write probes have already ran, it’s not necessary to also run a read probe. +A write probe will effectively probe reads as well. + |