| title | TiDB-Lightning Monitoring | |
|---|---|---|
| summary | Learn about the monitor configuration and monitoring metrics of TiDB-Lightning. | |
| category | reference | |
| aliases |
|
Both tidb-lightning and tikv-importer supports metrics collection via Prometheus. This document introduces the monitor configuration and monitoring metrics of TiDB-Lightning.
- If TiDB-Lightning is installed using TiDB-Ansible, simply add the servers to the
[monitored_servers]section in theinventory.ini. Then the Prometheus server can collect their metrics. - If TiDB-Lightning is manually installed, follow the instructions below.
tikv-importer v2.1 uses Pushgateway to deliver
metrics. Configure tikv-importer.toml to recognize the Pushgateway with the following settings:
[metric]
# The Prometheus client push job name.
job = "tikv-importer"
# The Prometheus client push interval.
interval = "15s"
# The Prometheus Pushgateway address.
address = ""The metrics of tidb-lightning can be gathered directly by Prometheus as long as it is discovered. You can set the metrics port in tidb-lightning.toml:
[lightning]
# HTTP port for debugging and Prometheus metrics pulling (0 to disable)
pprof-port = 8289
...You need to configure Prometheus to make it discover the tidb-lightning server. For instance, you can directly add the server address to the scrape_configs section:
...
scrape_configs:
- job_name: 'tidb-lightning'
static_configs:
- targets: ['192.168.20.10:8289']This section explains the monitoring metrics of tikv-importer and tidb-lightning.
Metrics provided by tikv-importer are listed under the namespace tikv_import_*.
-
tikv_import_rpc_duration(Histogram)Bucketed histogram for the duration of an RPC action. Labels:
- request:
switch_mode/open_engine/write_engine/close_engine/import_engine/cleanup_engine/compact_cluster/upload/ingest/compact - result:
ok/error
- request:
-
tikv_import_write_chunk_bytes(Histogram)Bucketed histogram for the uncompressed size of a block of KV pairs received from Lightning.
-
tikv_import_write_chunk_duration(Histogram)Bucketed histogram for the time needed to receive a block of KV pairs from Lightning.
-
tikv_import_upload_chunk_bytes(Histogram)Bucketed histogram for the compressed size of a chunk of SST file uploaded to TiKV.
-
tikv_import_upload_chunk_duration(Histogram)Bucketed histogram for the time needed to upload a chunk of SST file to TiKV.
-
tikv_import_range_delivery_duration(Histogram)Bucketed histogram for the time needed to deliver a range of KV pairs into a
dispatch-job. -
tikv_import_split_sst_duration(Histogram)Bucketed histogram for the time needed to split off a range from the engine file into a single SST file.
-
tikv_import_sst_delivery_duration(Histogram)Bucketed histogram for the time needed to deliver an SST file from a
dispatch-jobto anImportSSTJob. -
tikv_import_sst_recv_duration(Histogram)Bucketed histogram for the time needed to receive an SST file from a
dispatch-jobin anImportSSTJob. -
tikv_import_sst_upload_duration(Histogram)Bucketed histogram for the time needed to upload an SST file from an
ImportSSTJobto a TiKV node. -
tikv_import_sst_chunk_bytes(Histogram)Bucketed histogram for the compressed size of the SST file uploaded to a TiKV node.
-
tikv_import_sst_ingest_duration(Histogram)Bucketed histogram for the time needed to ingest an SST file into TiKV.
-
tikv_import_each_phase(Gauge)Indicates the running phase. Possible values are 1, meaning running inside the phase, and 0, meaning outside the phase. Labels:
- phase:
prepare/import
- phase:
-
tikv_import_wait_store_available_count(Counter)Counts the number of times a TiKV node is found to have insufficient space when uploading SST files. Labels:
- store_id: The TiKV store ID.
Metrics provided by tidb-lightning are listed under the namespace lightning_*.
-
lightning_importer_engine(Counter)Counts open and closed engine files. Labels:
- type:
open/closed
- type:
-
lightning_idle_workers(Gauge)Counts idle workers. Values should be less than the
*-concurrencysettings and are typically zero. Labels:- name:
table/index/region/io/closed-engine
- name:
-
lightning_kv_encoder(Counter)Counts open and closed KV encoders. KV encoders are in-memory TiDB instances that convert SQL
INSERTstatements into KV pairs. The net values need to be bounded in a healthy situation. Labels:- type:
open/closed
- type:
-
lightning_tables(Counter)Counts number of tables processed and their status. Labels:
- state:
pending/written/closed/imported/altered_auto_inc/checksum/analyzed/completed - result:
success/failure
- state:
-
lightning_engines(Counter)Counts number of engine files processed and their status. Labels:
- state:
pending/written/closed/imported/completed - result:
success/failure
- state:
-
lightning_chunks(Counter)Counts number of chunks processed and their status. Labels:
- state:
estimated/pending/running/finished/failed
- state:
-
lightning_import_seconds(Histogram)Bucketed histogram for the time needed to import a table.
-
lightning_row_read_bytes(Histogram)Bucketed histogram for the size of a single SQL row.
-
lightning_row_encode_seconds(Histogram)Bucketed histogram for the time needed to encode a single SQL row into KV pairs.
-
lightning_row_kv_deliver_seconds(Histogram)Bucketed histogram for the time needed to deliver a set of KV pairs corresponding to one single SQL row.
-
lightning_block_deliver_seconds(Histogram)Bucketed histogram for the time needed to deliver a block of KV pairs to Importer.
-
lightning_block_deliver_bytes(Histogram)Bucketed histogram for the uncompressed size of a block of KV pairs delivered to Importer.
-
lightning_chunk_parser_read_block_seconds(Histogram)Bucketed histogram for the time needed by the data file parser to read a block.
-
lightning_checksum_seconds(Histogram)Bucketed histogram for the time needed to compute the checksum of a table.
-
lightning_apply_worker_seconds(Histogram)Bucketed histogram for the time needed to acquire an idle worker. Labels:
- name:
table/index/region/io/closed-engine
- name: