v8.5.5: include storage engines in slow query logs and statements summary (#21155) (#22249)

Author: ti-chi-bot

identify-slow-queries.md

@@ -167,6 +167,11 @@ Fields related to Resource Control:
 * `Request_unit_write`: the total write RUs consumed by the statement.
 * `Time_queued_by_rc`: the total time that the statement waits for available resources.
 
+Fields related to storage engines:
+
+- `Storage_from_kv`: introduced in v8.5.5, indicates whether this statement read data from TiKV.
+- `Storage_from_mpp`: introduced in v8.5.5, indicates whether this statement read data from TiFlash.
+
 ## Related system variables
 
 * [`tidb_slow_log_threshold`](/system-variables.md#tidb_slow_log_threshold): Sets the threshold for the slow log. The SQL statement whose execution time exceeds this threshold is recorded in the slow log. The default value is 300 (ms).

statement-summary-tables.md

@@ -455,6 +455,11 @@ Fields related to Resource Control:
 - `MAX_QUEUED_RC_TIME`: the maximum waiting time for available RU when executing SQL statements.
 - `RESOURCE_GROUP`: the resource group bound to SQL statements.
 
+Fields related to storage engines:
+
+- `STORAGE_KV`: introduced in v8.5.5, indicates whether the previous execution of SQL statements of this category read data from TiKV.
+- `STORAGE_MPP`: introduced in v8.5.5, indicates whether the previous execution of SQL statements of this category read data from TiFlash.
+
 ### `statements_summary_evicted` fields description
 
 - `BEGIN_TIME`: Records the starting time.