metrics_diag_no_workload: There is no advice for clusters without workloads.
metrics_diag_no_prod: There is no advice for non-production clusters because the number of TiKV instances is less than 3.
metrics_diag_143: The client type should be checked. If JDBC used, it is recommended to add a configuration as 'useServerPrepStmts=true&cachePrepStmts=true&prepStmtCacheSize=1000&prepStmtCacheSqlLimit=20480&useConfigs=maxPerformance'. It is better to communicate with end-users without JDBC clients about how to implement the application, cache prepared statement objects on the client side, not reset calls to StmtPrepare and StmtClose, and reduce the number of command calls required to execute each query from 3 to 1.
metrics_diag_144: The latency outside the TiDB cluster is much higher. It is recommended to check if there is an issue on the client side. The average connection idle duration is {{var_1}} ms and the average query handle duration in the TiDB cluster is {{var_2}} ms.
metrics_diag_145: The application on the client side might be optimized because of the low hit rate of plan cache.
metrics_diag_146: If the downward trend of QPS is not expected, please check the active connection counts first because they are high correlated.
metrics_diag_147: It is recommended to check the load balancer on the client side because the QPS are imbalance among the TiDB nodes.
metrics_diag_148: It is recommended to check the load balancer on the client side because the active connection counts are imbalance among the TiDB nodes.
metrics_diag_149: It is recommended to scale in/out TiKV because the minimum CPU usage is up to {{var_1}}%.
metrics_diag_150: It is recommended to scale in/out TiKV because the minimum disk usage is up to {{var_1}}%.
metrics_diag_151: It is recommended to scale in/out TiDB because the minimum CPU usage is up to {{var_1}}%.
metrics_diag_152: It is recommended to contact PingCAPers to enable plan cache on TiDB side, if the TiDB cluster version < v6.1.0. On-promise users could enable it by themselves.
metrics_diag_156: It is recommended to check the network environment because the latency between TiDB and TiKV is up to {{var_1}} ms.
metrics_diag_157: It is recommended to confirm if the application use the Statement Prepare interface sufficiently.
metrics_diag_159: It should be checked that the active connection counts increase with not increased QPS and worse latency.
metrics_diag_158: It is recommended to check if there is a hotspot because the CPU usages are imbalance among the TiKV nodes.
metrics_diag_160: It is recommended to check the root cause of increasing failed queries.
metrics_diag_161: It is recommended to check the load balancer on the client side or query types on TiDB side because the latency are imbalance among the TiDB nodes.
metrics_diag_162: It is recommended to check if there is a hotspot because the memory usages are imbalance among the TiKV nodes.
metrics_diag_163: It is recommended to check the TiDB cluster because the CPU usages are imbalance among the TiDB nodes.
metrics_diag_164: It is recommended to check the load balancer on the client side or slow queries because the memory usages are imbalance among the TiDB nodes.
metrics_diag_165: There might be an anomaly with MVCC because GC SafePoint works abnormally.
metrics_diag_166: The average P99 TiKV approximate region size is up to {{var_1}} MB. Check the configuration or bugs about split.
metrics_diag_153: The scatter scheduler should not be enabled in a production environment. Please contact PingCAPers to disable it.
metrics_diag_154: It is recommended to contact PingCAPers to enable Raft-engine, if v5.4.0 <= the TiDB cluster version < v6.1.0. On-promise users could enable it by themselves.
metrics_diag_155: It is recommended to contact PingCAPers to enable AsyncIO.
metrics_diag_167: Please check if PD schedulers runs as expected.
metrics_diag_168: Please check if the TiKV configuration raftstore.hibernate-regions is TRUE.
tidb_get_token_duration_38: TiDB gets tokens in {{var_1}} takes more than {{var_2}} ms, please increase token-limit.
tidb_diag_parser_duration_39: SQL parsing duration in {{var_1}} takes more than {{var_2}} ms, please use binary protocol.
tidb_diag_compile_duration_40: SQL compile duration in {{var_1}} takes more than {{var_2}} s, please use plan cache.
tidb_wait_tso_duration_43: TiDB wait for tso in {{var_1}} takes more than {{var_2}} ms, please check PD and network resource and scale it.
tidb_wait_tso_duration_44: PD receiving tso request in {{var_1}} takes more than {{var_2}} s, please check PD and network resource and scale it.
tikv_pessmistic_txn_conflict_51: The mean time of lock wait in {{var_1}} takes more than {{var_2}} s, please adjust pessimistic-txn.wait-for-lock-timeout, pessimistic-txn.wake-up-delay-duration, or make transaction commit faster, or Modify the service to reduce lock conflicts.
tikv_pessmistic_txn_conflict_5111: The number of lock wait in all tikv instanaces is over {{var_1}}, please adjust pessimistic-txn.wait-for-lock-timeout, pessimistic-txn.wake-up-delay-duration, or make transaction commit faster, or Modify the service to reduce lock conflicts.
tikv_raft_propose_wait_duration_78: The raft propose wait duarion in tikv {{var_1}} takes more than {{var_2}} s, please enable the asyncIO feature.
tikv_diag_mvcc_versions_too_many_85: Old MVCC versions are too many, please make gc faster.
tikv_diag_cop_task_duration_171: TiKV cop duration in {{var_1}} takes more than {{var_2}} s, please check old mvcc versions, tomstones and key range.