pingcap · ti-chi-bot · Dec 18, 2023 · Dec 14, 2023 · Dec 14, 2023 · Dec 14, 2023
diff --git a/grafana-tikv-dashboard.md b/grafana-tikv-dashboard.md
@@ -185,6 +185,21 @@ This section provides a detailed description of these key metrics on the **TiKV-
 
 ![TiKV Dashboard - Storage metrics](/media/tikv-dashboard-storage.png)
 
+### Flow Control
+
+- Scheduler flow: The scheduler traffic on each TiKV instance in real time.
+- Scheduler discard ratio: The rejection ratio of scheduler requests on each TiKV instance. If this ratio is greater than 0, it indicates that flow control exists. When `Compaction pending bytes` exceeds its threshold, TiKV will linearly increase the `Scheduler Discard Ratio` based on the exceeded portion. The client will retry the rejected requests automatically.
- Scheduler discard ratio: The rejection ratio of scheduler requests on each TiKV instance. If this ratio is greater than 0, it indicates that flow control exists. When `Compaction pending bytes` exceeds its threshold, TiKV will linearly increase the `Scheduler Discard Ratio` based on the exceeded portion. The client will retry the rejected requests automatically.
+- Scheduler discard ratio: The rejection ratio of scheduler requests on each TiKV instance. If this ratio is greater than 0, it indicates that flow control exists. When `Compaction pending bytes` exceeds its threshold, TiKV will linearly increase the `Scheduler discard ratio` based on the exceeded portion. The client will retry the rejected requests automatically.
- Scheduler discard ratio: The rejection ratio of scheduler requests on each TiKV instance. If this ratio is greater than 0, it indicates that flow control exists. When `Compaction pending bytes` exceeds its threshold, TiKV will linearly increase the `Scheduler Discard Ratio` based on the exceeded portion. The client will retry the rejected requests automatically.
+- Scheduler discard ratio: The rejection ratio of scheduler requests on each TiKV instance. If this ratio is greater than 0, it indicates that flow control exists. When `Compaction pending bytes` exceeds its threshold, TiKV will linearly increase the `Scheduler discard ratio` based on the exceeded portion. The client will retry the rejected requests automatically.
+- Throttle duration: The blocked duration for the execution of the scheduler requests when flow control is triggered due to too many L0 files. If this metric has values, it indicates that flow control exists.
+- Scheduler throttled CF: The CF that triggers RocksDB throttling when the flow control threshold is reached.
+- Flow controller actions: The actions that trigger RocksDB throttling when the flow control threshold is reached.
+- Flush/L0 flow: The traffic of flush and L0 compaction for different CFs of RocksDB on each TiKV instance.
+- Flow control factors: The factors related to triggering RocksDB throttling.
+- Compaction pending bytes: The size of the RocksDB data awaiting compaction in real time on each TiKV instance.
+- Txn command throttled duration: The blocked duration for commands related to transactions due to throttling. Under normal circumstances, this metric is 0.
+- Non-txn command throttled duration: The blocked duration for other commands due to throttling. Under normal circumstances, this metric is 0.
+
+![TiKV Dashboard - Flow Control metrics](/media/tikv-dashboard-flow-control.png)
+
 ### Scheduler
 
 - Scheduler stage total: The number of commands at each stage per second. There should not be a lot of errors in a short time.

diff --git a/media/tikv-dashboard-flow-control.png b/media/tikv-dashboard-flow-control.png