Skip to main content



taosKeeper is a tool for TDengine that exports monitoring metrics. With taosKeeper, you can easily monitor the operational status of your TDengine deployment. taosKeeper uses the TDengine REST API. It is not necessary to install TDengine Client to use taosKeeper.


There are two ways to install taosKeeper: Methods of installing taosKeeper:

  • Installing the official TDengine installer will automatically install taosKeeper. Please refer to TDengine installation for details.

  • You can compile taosKeeper separately and install it. Please refer to the taosKeeper repository for details.

Configuration and Launch


taosKeeper needs to be executed on the terminal of the operating system, it supports three configuration methods: Command-line arguments, environment variable and configuration file. The precedence of those is Command-line, environment variable and configuration file.

Make sure that the TDengine cluster is running correctly before running taosKeeper. Ensure that the monitoring service in TDengine has been started. At least the values of monitor and monitorFqdn need to be set in taos.cfg.

monitor 1
monitorFqdn localhost # taoskeeper's FQDN

For more information, see TDengine Monitoring Configuration.

Quick Launch

After the installation is complete, run the following command to start the taoskeeper service:

systemctl start taoskeeper

Run the following command to confirm that taoskeeper is running normally:

systemctl status taoskeeper

Output similar to the following indicates that taoskeeper is running normally:

Active: active (running)

Output similar to the following indicates that taoskeeper has not started successfully:

Active: inactive (dead)

The following systemctl commands can help you manage taoskeeper service:

  • Start taoskeeper Server: systemctl start taoskeeper

  • Stop taoskeeper Server: systemctl stop taoskeeper

  • Restart taoskeeper Server: systemctl restart taoskeeper

  • Check taoskeeper Server status: systemctl status taoskeeper

  • The systemctl command requires root privileges. If you are not logged in as the root user, use the sudo command.
  • The systemctl stop taoskeeper command will instantly stop taoskeeper Server.
  • If your system does not include systemd, you can run /usr/local/taos/bin/taoskeeper to start taoskeeper manually.

Launch With Configuration File

You can quickly launch taosKeeper with the following commands. If you do not specify a configuration file, /etc/taos/taoskeeper.toml is used by default. If this file does not specify configurations, the default values are used.

$ taoskeeper -c <keeper config file>

Sample configuration files

# enable debug in gin framework
debug = false

# listen to server port, default 6043
port = 6043

# set log level to panic, error, info, debug, or trace
loglevel = "info"

# set pool size
gopoolsize = 50000

# query rotation period for TDengine monitoring data
RotationInterval = "15s"

host = ""
port = 6041
username = "root"
password = "taosdata"

# set taosAdapter to monitor
address = ["",""]

# monitoring metric prefix
prefix = "taos"

# cluster data identifier
cluster = "production"

# database to store monitoring data
database = "log"

# standard tables to monitor
tables = ["normal_table"]

# database options for db storing metrics data
cachemodel = "none"

Obtain Monitoring Metrics

taosKeeper records monitoring metrics generated by TDengine in a specified database and provides an interface through which you can export the data.

View Monitoring Results

$ taos
# the log database is used in this example
> use log;
> select * from cluster_info limit 1;

Example result set:

           ts            |            first_ep            | first_ep_dnode_id |   version    |    master_uptime     | monitor_interval |  dbs_total  |  tbs_total  | stbs_total  | dnodes_total | dnodes_alive | mnodes_total | mnodes_alive | vgroups_total | vgroups_alive | vnodes_total | vnodes_alive | connections_total |  protocol   |           cluster_id           |
2022-08-16 17:37:01.629 | hlb:6030 | 1 | | 0.27250 | 15 | 2 | 27 | 38 | 1 | 1 | 1 | 1 | 4 | 4 | 4 | 4 | 14 | 1 | 5981392874047724755 |
Query OK, 1 rows in database (0.036162s)

Export Monitoring Metrics

$ curl

Sample result set (excerpt):

# HELP taos_cluster_info_connections_total
# TYPE taos_cluster_info_connections_total counter
taos_cluster_info_connections_total{cluster_id="5981392874047724755"} 16
# HELP taos_cluster_info_dbs_total
# TYPE taos_cluster_info_dbs_total counter
taos_cluster_info_dbs_total{cluster_id="5981392874047724755"} 2
# HELP taos_cluster_info_dnodes_alive
# TYPE taos_cluster_info_dnodes_alive counter
taos_cluster_info_dnodes_alive{cluster_id="5981392874047724755"} 1
# HELP taos_cluster_info_dnodes_total
# TYPE taos_cluster_info_dnodes_total counter
taos_cluster_info_dnodes_total{cluster_id="5981392874047724755"} 1
# HELP taos_cluster_info_first_ep
# TYPE taos_cluster_info_first_ep gauge
taos_cluster_info_first_ep{cluster_id="5981392874047724755",value="hlb:6030"} 1


$ curl -i


HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
Date: Mon, 03 Apr 2023 07:20:38 GMT
Content-Length: 19


taoskeeper with Prometheus

There is /metrics api in taoskeeper provide TDengine metric data for Prometheus.

scrape config

Scrape config in Prometheus specifies a set of targets and parameters describing how to scrape metric data from endpoint. For more information, please reference to Prometheus documents.

# A scrape configuration containing exactly one endpoint to scrape:
# Here it's Prometheus itself.
- job_name: "taoskeeper"
# metrics_path defaults to '/metrics'
# scheme defaults to 'http'.
- targets: ["localhost:6043"]


There is a dashboard named TaosKeeper Prometheus Dashboard for 3.x, which provides a monitoring dashboard similar to TInsight.

In Grafana, click the Dashboard menu and click import, enter the dashboard ID 18587 and click the Load button. Then finished importing TaosKeeper Prometheus Dashboard for 3.x dashboard.