We are currently refactoring our documentation. Please excuse any problems you may find and report them here.

Currently, you can use two types of interfaces to monitor the state of the TiKV cluster:

  • The component state interface: use the HTTP interface to get the internal information of a component, which is called the component state interface.
  • The metrics interface: use the Prometheus interface to record the detailed information of various operations in the components, which is called the metrics interface.

The component state interface

You can use this type of interface to monitor the basic information of components. This interface can get the details of the entire TiKV cluster and can act as the interface to monitor Keepalive.

The PD server

The API address of the Placement Driver (PD) is http://${host}:${port}/pd/api/v1/${api_name}

The default port number is 2379.

For detailed information about various API names, see PD API doc.

You can use the interface to get the state of all the TiKV instances and the information about load balancing. It is the most important and frequently-used interface to get the state information of all the TiKV nodes. See the following example for the information about a 3-instance TiKV cluster deployed on a single machine:

  1. curl http://127.0.0.1:2379/pd/api/v1/stores
  2. {
  3.   "count": 3,
  4.   "stores": [
  5.     {
  6.       "store": {
  7.         "id": 1,
  8.         "address": "127.0.0.1:20161",
  9.         "version": "2.1.0-rc.2",
  10.         "state_name": "Up"
  11.       },
  12.       "status": {
  13.         "capacity": "937 GiB",
  14.         "available": "837 GiB",
  15.         "leader_weight": 1,
  16.         "region_count": 1,
  17.         "region_weight": 1,
  18.         "region_score": 1,
  19.         "region_size": 1,
  20.         "start_ts": "2018-09-29T00:05:47Z",
  21.         "last_heartbeat_ts": "2018-09-29T00:23:46.227350716Z",
  22.         "uptime": "17m59.227350716s"
  23.       }
  24.     },
  25.     {
  26.       "store": {
  27.         "id": 2,
  28.         "address": "127.0.0.1:20162",
  29.         "version": "2.1.0-rc.2",
  30.         "state_name": "Up"
  31.       },
  32.       "status": {
  33.         "capacity": "937 GiB",
  34.         "available": "837 GiB",
  35.         "leader_weight": 1,
  36.         "region_count": 1,
  37.         "region_weight": 1,
  38.         "region_score": 1,
  39.         "region_size": 1,
  40.         "start_ts": "2018-09-29T00:05:47Z",
  41.         "last_heartbeat_ts": "2018-09-29T00:23:45.65292648Z",
  42.         "uptime": "17m58.65292648s"
  43.       }
  44.     },
  45.     {
  46.       "store": {
  47.         "id": 7,
  48.         "address": "127.0.0.1:20160",
  49.         "version": "2.1.0-rc.2",
  50.         "state_name": "Up"
  51.       },
  52.       "status": {
  53.         "capacity": "937 GiB",
  54.         "available": "837 GiB",
  55.         "leader_count": 1,
  56.         "leader_weight": 1,
  57.         "leader_score": 1,
  58.         "leader_size": 1,
  59.         "region_count": 1,
  60.         "region_weight": 1,
  61.         "region_score": 1,
  62.         "region_size": 1,
  63.         "start_ts": "2018-09-29T00:05:47Z",
  64.         "last_heartbeat_ts": "2018-09-29T00:23:44.853636067Z",
  65.         "uptime": "17m57.853636067s"
  66.       }
  67.     }
  68.   ]
  69. }

The metrics interface

You can use this type of interface to monitor the state and performance of the entire cluster. The metrics data is displayed in Prometheus and Grafana. See Use Prometheus and Grafana for how to set up the monitoring system.

You can get the following metrics for each component:

The PD server

  • the total number of times that the command executes
  • the total number of times that a certain command fails
  • the duration that a command succeeds
  • the duration that a command fails
  • the duration that a command finishes and returns result

The TiKV server

  • Garbage Collection (GC) monitoring
  • the total number of times that the TiKV command executes
  • the duration that Scheduler executes commands
  • the total number of times of the Raft propose command
  • the duration that Raft executes commands
  • the total number of times that Raft commands fail
  • the total number of times that Raft processes the ready state

Use Prometheus and Grafana

This section introduces the deployment architecture of Prometheus and Grafana in TiKV, and how to set up and configure the monitoring system.

The deployment architecture

See the following diagram for the deployment architecture:

Monitoring a Cluster - 图1

Figure 1. Monitor architecture

You must add the Prometheus Pushgateway addresses to the startup parameters of the PD and TiKV components.

Set up the monitoring system

See the following links for your reference:

Manual configuration

This section describes how to manually configure PD and TiKV, PushServer, Prometheus, and Grafana.

Note: If your TiKV cluster is deployed using Ansible or Docker Compose, the configuration is automatically done, and generally, you do not need to configure it manually again. If your TiKV cluster is deployed using Docker, you can follow the configuration steps below.

Configure PD and TiKV

  • PD: update the toml configuration file with the Pushgateway address and the the push frequency:

    1. [metric]
    2. # prometheus client push interval, set "0s" to disable prometheus.
    3. interval = "15s"
    4. # prometheus pushgateway address, leaves it empty will disable prometheus.
    5. address = "host:port"

  • TiKV: update the toml configuration file with the Pushgateway address and the the push frequency. Set the job field to "tikv".

    1. [metric]
    2. # the Prometheus client push interval. Setting the value to 0s stops Prometheus client from pushing.
    3. interval = "15s"
    4. # the Prometheus pushgateway address. Leaving it empty stops Prometheus client from pushing.
    5. address = "host:port"
    6. # the Prometheus client push job name. Note: A node id will automatically append, e.g., "tikv_1".
    7. job = "tikv"

Configure PushServer

Generally, you can use the default port 9091 and do not need to configure PushServer.

Configure Prometheus

Add the Pushgateway address to the yaml configuration file:

  1. global:
  2.   scrape_interval:     15s  # By default, scrape targets every 15 seconds.
  3.   evaluation_interval: 15s  # By default, scrape targets every 15 seconds.
  4.   # scrape_timeout is set to the global default value (10s).
  5.     external_labels:
  6.       cluster: 'test-cluster'
  7.       monitor: "prometheus"
  9. scrape_configs:
  10.   - job_name: 'pd'
  11.     honor_labels: true  # Do not overwrite job & instance labels.
  12.     static_configs:
  13.     - targets:
  14.       - '192.168.199.113:2379'
  15.       - '192.168.199.114:2379'
  16.       - '192.168.199.115:2379'
  18.   - job_name: 'tikv'
  19.     honor_labels: true  # Do not overwrite job & instance labels.
  20.     static_configs:
  21.     - targets:
  22.       - '192.168.199.116:20180'
  23.       - '192.168.199.117:20180'
  24.       - '192.168.199.118:20180'

Configure Grafana

Create a Prometheus data source

  1. Log in to the Grafana Web interface.
  2. Click the Grafana logo to open the sidebar menu.
  3. Click “Data Sources” in the sidebar.
  4. Click “Add data source”.
  5. Specify the data source information:
    • Specify the name for the data source.
    • For Type, select Prometheus.
    • For Url, specify the Prometheus address.
    • Specify other fields as needed.
  6. Click “Add” to save the new data source.

Create a Grafana dashboard

  1. Click the Grafana logo to open the sidebar menu.
  2. On the sidebar menu, click “Dashboards” -> “Import” to open the “Import Dashboard” window.
  3. Click “Upload .json File” to upload a JSON file (Examples can be found in tidb-ansible).
  4. Click “Save & Open”.
  5. A Prometheus dashboard is created.