TiDB Monitoring Interface: Unable to Track SQL Statements

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: tidb监控界面,监测不到sql语句

| username: 艾维iii

The TiDB monitoring interface is not detecting SQL statements.

| username: 这里介绍不了我 | Original post link

Is this cluster newly set up?

| username: 艾维iii | Original post link

No, it could be monitored before.

| username: 这里介绍不了我 | Original post link

Check the logs of the Dashboard node.

| username: 艾维iii | Original post link

Okay, it seems like it’s his problem. Restarting didn’t solve it either.

| username: 这里介绍不了我 | Original post link

At the same time, compare Grafana and check if there are any anomalies in the UI of this node.

| username: 艾维iii | Original post link

No problem.

| username: juecong | Original post link

Did you disable the top SQL feature?

| username: 艾维iii | Original post link

I haven’t done any related operations. The main issue now is that there is no data in the various metric charts on the monitoring interface.

| username: 这里介绍不了我 | Original post link

Look for the PD log with the status Up|UI, not Grafana. The Dashboard is on a specific PD, with |L indicating that the PD is the Leader, and |UI indicating that the PD is running TiDB Dashboard.

| username: Kongdom | Original post link

This is the Grafana log, right? You need to check the corresponding PD node log.

| username: 艾维iii | Original post link

Okay, let’s take a look.

| username: shigp_TIDBER | Original post link

The topsql feature can be turned on and off online. Check if it has been turned off.

| username: 艾维iii | Original post link

Opened it, but there’s no data.

| username: 艾维iii | Original post link

No error reported

| username: DBAER | Original post link

Is the cluster functioning normally now?

| username: 艾维iii | Original post link

The cluster is functioning normally.

| username: Kongdom | Original post link

Have you done anything recently?

| username: 艾维iii | Original post link

No, I haven’t done anything to the cluster.

| username: 艾维iii | Original post link

The Grafana interface is not monitoring any information.

t=2024-05-16T15:00:16+0800 lvl=info msg="Alert Rule returned no data" logger=alerting.evalContext ruleId=24 name="Scheduler worker CPU alert" changing state to=no_data
t=2024-05-16T15:00:18+0800 lvl=info msg="Alert Rule returned no data" logger=alerting.evalContext ruleId=68 name="gRPC poll CPU alert" changing state to=no_data
t=2024-05-16T15:00:18+0800 lvl=info msg="Alert Rule returned no data" logger=alerting.evalContext ruleId=39 name="Store writer CPU alert" changing state to=ok
t=2024-05-16T15:00:18+0800 lvl=info msg="Alert Rule returned no data" logger=alerting.evalContext ruleId=77 name="TiKV async apply CPU alert" changing state to=ok
t=2024-05-16T15:00:18+0800 lvl=info msg="Alert Rule returned no data" logger=alerting.evalContext ruleId=67 name="PD TSO RPC Duration alert" changing state to=no_data
t=2024-05-16T15:00:18+0800 lvl=info msg="Alert Rule returned no data" logger=alerting.evalContext ruleId=78 name="TiKV scheduler worker CPU alert" changing state to=ok
t=2024-05-16T15:00:18+0800 lvl=info msg="Alert Rule returned no data" logger=alerting.evalContext ruleId=40 name="TiKV gRPC poll CPU alert" changing state to=ok
t=2024-05-16T15:00:18+0800 lvl=info msg="Alert Rule returned no data" logger=alerting.evalContext ruleId=27 name="Append log duration alert" changing state to=no_data
t=2024-05-16T15:00:20+0800 lvl=info msg="Alert Rule returned no data" logger=alerting.evalContext ruleId=30 name="Async apply CPU alert" changing state to=no_data
t=2024-05-16T15:00:21+0800 lvl=info msg="Alert Rule returned no data" logger=alerting.evalContext ruleId=31 name="region health alert" changing state to=keep_state
t=2024-05-16T15:00:21+0800 lvl=info msg="Alert Rule returned no data" logger=alerting.evalContext ruleId=34 name="server report failures alert" changing state to=ok
t=2024-05-16T15:00:24+0800 lvl=info msg="Alert Rule returned no data" logger=alerting.evalContext ruleId=74 name="TiKV channel full alert" changing state to=ok
t=2024-05-16T15:00:24+0800 lvl=info msg="Alert Rule returned no data" logger=alerting.evalContext ruleId=35 name="TiKV channel full alert" changing state to=ok
t=2024-05-16T15:00:24+0800 lvl=info msg="Alert Rule returned no data" logger=alerting.evalContext ruleId=73 name="server report failures alert" changing state to=ok
t=2024-05-16T15:00:24+0800 lvl=info msg="Alert Rule returned no data" logger=alerting.evalContext ruleId=36 name="approximate region size alert" changing state to=no_data
t=2024-05-16T15:00:25+0800 lvl=info msg="Alert Rule returned no data" logger=alerting.evalContext ruleId=59 name="Connection Count alert" changing state to=no_data
t=2024-05-16T15:00:25+0800 lvl=info msg="Alert Rule returned no data" logger=alerting.evalContext ruleId=49 name="TiKV channel full alert" changing state to=ok
t=2024-05-16T15:00:25+0800 lvl=info msg="Alert Rule returned no data" logger=alerting.evalContext ruleId=37 name="TiKV raft store CPU alert" changing state to=ok
t=2024-05-16T15:00:25+0800 lvl=info msg="Alert Rule returned no data" logger=alerting.evalContext ruleId=48 name="server report failures alert" changing state to=ok
t=2024-05-16T15:00:26+0800 lvl=info msg="Alert Rule returned no data" logger=alerting.evalContext ruleId=42 name="TiKV Storage ReadPool CPU alert" changing state to=ok
t=2024-05-16T15:00:26+0800 lvl=info msg="Alert Rule returned no data" logger=alerting.evalContext ruleId=43 name="Unified read pool CPU alert" changing state to=ok
t=2024-05-16T15:00:26+0800 lvl=info msg="Alert Rule returned no data" logger=alerting.evalContext ruleId=66 name="KV Backoff OPS alert" changing state to=no_data