Important

You are viewing the documentation of TiDB v6.0 (DMR). PingCAP does not provide bug fixes for v6.0. Any bugs will be fixed in future releases.

For general purposes, please use the latest LTS version of the TiDB database.

TiDB Dashboard FAQ

This document summarizes the frequently asked questions (FAQs) and answers about TiDB Dashboard. If a problem cannot be located or persists after you perform as instructed, contact PingCAP technical support for help.

When the firewall or reverse proxy is configured, I am redirected to an internal address other than TiDB Dashboard

When multiple Placement Driver (PD) instances are deployed in a cluster, only one of the PD instances actually runs the TiDB Dashboard service. If you access other PD instances instead of this one, your browser redirects you to another address. If the firewall or reverse proxy is not properly configured for accessing TiDB Dashboard, when you visit the Dashboard, you might be redirected to an internal address that is protected by the firewall or reverse proxy.

When TiDB Dashboard is deployed with dual network interface cards (NICs), TiDB Dashboard cannot be accessed using another NIC

For security reasons, TiDB Dashboard on PD only monitors the IP addresses specified during deployment (that is, it only listens on one NIC), not on 0.0.0.0. Therefore, when multiple NICs are installed on the host, you cannot access TiDB Dashboard using another NIC.

If you have deployed TiDB using the tiup cluster or tiup playground command, currently this problem cannot be solved. It is recommended that you use a reverse proxy to safely expose TiDB Dashboard to another NIC. For details, see Use TiDB Dashboard behind a Reverse Proxy.

A prometheus_not_found error is shown in QPS and Latency sections on the Overview page

The QPS and Latency sections on the Overview page require a cluster with Prometheus deployed. Otherwise, the error is shown. You can solve this problem by deploying a Prometheus instance in the cluster.

If you still encounter this problem when the Prometheus instance has been deployed, the possible reason is that your deployment tool is out of date (TiUP or TiDB Operator), and your tool does not automatically report metrics addresses, which makes TiDB Dashboard unable to query metrics. You can upgrade you deployment tool to the latest version and try again.

If your deployment tool is TiUP, take the following steps to solve this problem. For other deployment tools, refer to the corresponding documents of those tools.

  1. Upgrade TiUP and TiUP Cluster:

    tiup update --self
    tiup update cluster --force
    
  2. After the upgrade, when a new cluster is deployed with Prometheus instances, the metrics can be displayed normally.

  3. After the upgrade, for an existing cluster, you can restart this cluster to report the metrics addresses. Replace CLUSTER_NAME with the actual cluster name:

    tiup cluster start CLUSTER_NAME
    

    Even if the cluster has been started, still execute this command. This command does not affect the normal application in the cluster, but refreshes and reports the metrics addresses, so that the monitoring metrics can be displayed normally in TiDB Dashboard.

An invalid connection error is shown on the Slow Queries page

The possible reason is that you have enabled the prepared-plan-cache feature of TiDB. As an experimental feature, when enabled, prepared-plan-cache might not function properly in specific TiDB versions, which could cause this problem in TiDB Dashboard (and other applications). You can disable prepared-plan-cache by updating TiDB Configuration file to solve this problem.

A required component NgMonitoring is not started error is shown

NgMonitoring is an advanced monitoring component built in TiDB clusters of v5.4.0 and later versions to support TiDB Dashboard features such as Continuous Profiling and Top SQL. NgMonitoring is automatically deployed when you deploy or upgrade a cluster with a newer version of TiUP. For clusters deployed using TiDB Operator, you can deploy NgMonitoring manually by referring to Enable Continuous Profiling.

If the web page shows required component NgMonitoring is not started, you can troubleshoot the deployment issue as follows:

Clusters Deployed using TiUP

Step 1. Check versions

  1. Check the TiUP cluster version. NgMonitoring is deployed only when TiUP is v1.9.0 or later.

    tiup cluster --version
    

    The command output shows the TiUP version. For example:

    tiup version 1.9.0 tiup
    Go Version: go1.17.2
    Git Ref: v1.9.0
    
  2. If the TiUP cluster version is earlier than v1.9.0, upgrade TiUP and TiUP cluster to the latest version:

    tiup update --all
    

Step 2. Add the ng_port configuration item on the control machine by using TiUP. Then reload Prometheus.

  1. Open the cluster configuration file in editing mode:

    tiup cluster edit-config ${cluster-name}
    
  2. Under monitoring_servers, add the ng_port:12020 parameter:

    monitoring_servers:
    - host: 172.16.6.6
      ng_port: 12020
    
  3. Reload Prometheus:

    tiup cluster reload ${cluster-name} --role prometheus
    

Please Contact PingCAP Technical Support for help if the error message is still prompted after performing steps above.

Clusters Deployed using TiDB Operator

Deploy the NgMonitoring component by following instructions in the Enable Continuous Profiling section in TiDB Operator documentation.

Clusters Started using TiUP Playground

When starting the cluster, TiUP Playground (>= v1.8.0) automatically starts the NgMonitoring component. To update TiUP Playground to the latest version, run the following command:

tiup update --self
tiup update playground

An unknown field error is shown on the Slow Queries page

If the unknown field error appears on the Slow Queries page after the cluster upgrade, the error is related to a compatibility issue caused by the difference between TiDB Dashboard server fields (which might be updated) and user preferences fields (which are in the browser cache). This issue has been fixed. If your cluster is earlier than v5.0.3 or v4.0.14, perform the following steps to clear your browser cache:

  1. Open TiDB Dashboard page.

  2. Open Developer Tools. Different browsers have different ways of opening Developer Tools. After clicking the Menu Bar:

    • Firefox: Menu > Web Developer > Toggle Tools, or Tools > Web Developer > Toggle Tools.
    • Chrome: More tools > Developer tools.
    • Safari: Develop > Show Web Inspector. If you can't see the Develop menu, go to Safari > Preferences > Advanced, and check the Show Develop menu in menu bar checkbox.

    In the following example, Chrome is used.

    Opening DevTools from Chrome's main menu

  3. Select the Application panel, expand the Local Storage menu and select the TiDB Dashboard page domain. Click the Clear All button.

    Clear the Local Storage

Was this page helpful?