README
¶
Grafana Plugin for TDengine
- Installation
- Usage
- Important changes
- Monitor TDengine Database with TDengine Data Source Plugin
- Docker Stack
- Dashboards
TDengine is open-sourced big data platform under GNU AGPL v3.0, designed and optimized for the Internet of Things (IoT), Connected Cars, Industrial IoT, and IT Infrastructure and Application Monitoring, developed by TDengine.
TDengine data source plugin is developed for Grafana. This document explains how to install and configure the data source plugin, and use it as a time-series database. We'll take a look at the data source options, variables, querying, and other options specific to this data source.
At first, please refer to Add a data source for instructions on how to add a data source to Grafana. Note that, only users with the organization admin role can add data sources.
Installation
One-line installer
TDENGINE_DS_NAME=TDengine
TDENGINE_CLOUD_URL=
TDENGINE_CLOUD_TOKEN=
bash -c "$(curl -fsSL https://raw.githubusercontent.com/taosdata/grafanaplugin/master/install.sh)"
TDengine_DS_NAME
: The data source name to createTDENGINE_CLOUD_URL
: The TDengine url, eg.http://localhost:6041
TDENGINE_CLOUD_TOKEN
: The TDengine cloud service token, optional.TDENGINE_USER
/TDENGINE_PASSWORD
: The TDengine username/password, optional.
Type install.sh --help
for the full usage of the script.
Install with GUI
The TDengine data source plugin is already published as a signed Grafana plugin. You can easily install it from Grafana Configuration GUI. In any platform you already installed Grafana, you can open the URL http://localhost:3000 then click plugin menu from left panel.
Then key in TDengine
to search.
Install Manually
We recommend you use the prebuilt package of the plugin in github latest release download page.
Option 1, you can install the TDengine data source plugin with grafana-cli
.
sudo -u grafana grafana-cli \
--pluginUrl https://github.com/taosdata/grafanaplugin/releases/download/v3.1.3/tdengine-datasource-3.1.3.zip \
plugins install tdengine-datasource
Option 2, you can install the plugin manually.
# make sure to use the right plugins directory
GF_PLUGINS_DIR=/var/lib/grafana/plugins
# install plugin
V=3.1.7
wget -c https://github.com/taosdata/grafanaplugin/releases/download/v$V/tdengine-datasource-$V.zip
sudo -u grafana unzip -oq tdengine-datasource-$V.zip -d $GF_PLUGINS_DIR
sudo -u grafana sh -c "chmod +x $GF_PLUGINS_DIR/tdengine-datasource/tdengine-datasource*"
Here is a unified shell script to automatically download and install the latest plugin in a Grafana server.
# make sure to use the right plugins directory
GF_PLUGINS_DIR=/var/lib/grafana/plugins
get_latest_release() {
curl --silent "https://api.github.com/repos/taosdata/grafanaplugin/releases/latest" |
grep '"tag_name":' |
sed -E 's/.*"v([^"]+)".*/\1/'
}
install_plugin() {
V=$1
[ -f tdengine-datasource-$V.zip ] ||
wget -c https://github.com/taosdata/grafanaplugin/releases/download/v$V/tdengine-datasource-$V.zip
sudo -u grafana unzip -oq tdengine-datasource-$V.zip -d $GF_PLUGINS_DIR
sudo -u grafana sh -c "chmod +x $GF_PLUGINS_DIR/tdengine-datasource/tdengine-datasource*"
}
install_plugin $(get_latest_release)
Option 3, if you use the plugin in docker, just set the environment GF_INSTALL_PLUGINS
like GF_INSTALL_PLUGINS=https://github.com/taosdata/grafanaplugin/releases/download/v3.1.3/tdengine-datasource-3.1.3.zip;tdengine-datasource
, or refer to Build and run a Docker image with pre-installed plugins to pre-build a custom Grafana image with the TDengine data source plugin.
Option 4, build and install this plugin by yourself. You should following the CONTRIBUTING steps to setup develop environment and build the plugin.
yarn build:all
Then copy the dist/
directory to Grafana plugin directory.
sudo -u grafana rsync -rlzP dist/ /var/lib/grafana/plugins/tdengine-datasource
It will also generate a zipped package named tdengine-datasource-<version>.zip
for distribution.
Note that the plugin has not been published to https://grafana.com officially (the plugin is under review, as if you want to know) - that means the plugin is unsigned for public use. So if you use it in 7.x and 8.x of grafana, you should configure in /etc/grafana/grafana.ini
by add these lines to allow unsigned plugin before start the Grafana server.
[plugins]
allow_loading_unsigned_plugins = tdengine-datasource
Or use environment variable GF_ALLOW_LOADING_UNSIGNED_PLUGINS=tdengine-datasource
in docker and other container-based environments.
In any particular scenario, if you need a signed plugin, please follow the Sign a plugin instructions to sign a private plugin. Commands may be like this:
export GRAFANA_API_KEY=<YOUR_API_KEY>
yarn run grafana-toolkit plugin:sign \
--signatureType private \
--rootUrls 'http://localhost:3000'
rootUrls
is your local grafana server url.
The next step is restart the Grafana server. The new data source should now be available in the data source type dropdown in the Add Data Source view. For systemd based system, the restart command is:
sudo systemctl restart grafana-server
For SysVInit based system (CentOS 6 etc.):
sudo service grafana-server restart
Installation on macOS
The best way to install Grafana is to use Homebrew with which to install the most recent released version of Grafana using Homebrew package.
Open a terminal and enter:
brew update
brew install grafana
Next, add TDengine’s plugin with the following command:
sudo grafana-cli --pluginsDir /opt/homebrew/var/lib/grafana/plugins --pluginUrl\
https://github.com/taosdata/grafanaplugin/releases/download/v3.1.3/tdengine-datasource-3.1.3.zip \
plugins install tdengine-datasource
The pluginsDir
option /opt/homebrew/var/lib/grafana/plugins
should be override if the directory not exist(that will depend on how you install the Grafana service).
You can check the plugins directory to see if tdengine-datasource plugin installed:
$ ls /opt/homebrew/var/lib/grafana/plugins
tdengine-datasource
TDengine plugin has not been signed, so you should change the grafana configuration to allow unsigned plugin.
Since you are using macOS with Homebrew, Grafana instances installed using Homebrew require you to edit the grafana.ini
file directly. The way to change the grafana.ini
file is to run the following command:
open -a textedit /opt/homebrew/etc/grafana/grafana.ini
Note that, this plugin is signed since v3.1.7. If you are using an older version, please configure to allow loading unsigned plugins:
First, open the file, search for
;allow_loading_unsigned_plugins
Then, delete the semicolon to uncomment it, and change the line to:
allow_loading_unsigned_plugins = tdengine-datasource
After that, go ahead and save the configuration file.
(Re-)start Grafana service:
# brew services start grafana
brew services restart grafana
Point to plugins pages to search and check TDengine plugin is in the list.
Usage
Now it's ready for you to add your own TDengine data source and use it in a dashboard. Refer to Grafana Datasource documentations topic - Add a data source for a quick view. Please make sure the TDengine backend daemon taosd
and TDengine RESTful service backend daemon taosadapter
already launched.
Add Data Source
Point to Configurations -> Data Sources menu and then Add data source button.
Search and choose TDengine.
If TDengine is not in the list, please check the installation instructions for allowing loading unsigned plugins.
Configure TDengine data source.
Save and test it, it should say 'TDengine Data source is working'.
Import Dashboard
Point to + / Create - import (or /assets/import
url).
Now you can import dashboard with JSON file or grafana dashboard id (please make sure your network is public to https://grafana.com).
Here is the first grafana dashboard you want to use for TDengine, the grafana dashboard id is 15146
.
After load:
After import:
Alert Feature
Now TDengine data source plugin provides basic alert feature support by backend plugin since version 3.1.0
. But it has some known limits currently:
- The sql statement only supports two variables:
$from
and$to
. - When using grafana's alert function, you must use
SQL
as theType
option. That means, arithmetic expression will not work as you expected for alert. - In addition, only
ALIAS BY
andINPUT SQL
are valid. So alert does not work if you requires the time-shift feature.
We've published a dashboard (15155) for you to understand how alert working.
Here is the details:
First, you should have a notification channel, if no, add a new one in http://localhost:3000/alerting/notification/new(here we use AlertManager for test, we also provides a webhook example here, in webhook/
directory)
Second, set the alert query in panel like this:
Config the alert rule and notifications:
Test it with Test rule button, it should return firing: true
:
In alert manager dashboard, you could see the alert:
Important changes
v3.2.0
-
TDengine data source plugin uses secureJsonData to store sensitive data. It will cause a breaking change when you upgrading from an older version:
The simple way to migrate from older version is to reconfigure the data source like adding a data source from scratch.
If you're using Grafana provisioning configurations, you should change the data source provisioning configuration file to use
secureJsonData
:apiVersion: 1 datasources: # <string, required> name of the datasource. Required - name: TDengine # <string, required> datasource type. Required type: tdengine-datasource # <string, required> access mode. direct or proxy. Required # <int> org id. will default to orgId 1 if not specified orgId: 1 # <string> url to TDengine rest api, eg. http://td1:6041 url: "$TDENGINE_API" # <bool> mark as default datasource. Max one per org isDefault: true # <map> secureJsonData: # <string> a redundant url configuration. Required. url: "$TDENGINE_API" # <string> basic authorization token. Required, can be build like # `printf root:taosdata|base64` basicAuth: "${TDENGINE_BASIC_AUTH}" # <string> cloud service token of TDengine, optional. token: "$TDENGINE_CLOUD_TOKEN" # aliSms* is configuration options for builtin sms notifier powered by Aliyun Cloud SMS # <string> the key id from Aliyun. aliSmsAccessKeyId: "$SMS_ACCESS_KEY_ID" # <string> key secret paired to key id. aliSmsAccessKeySecret: "$SMS_ACCESS_KEY_SECRET" aliSmsSignName: "$SMS_SIGN_NAME" # <string> sms template code from Aliyun. eg. SMS_123010240 aliSmsTemplateCode: "$SMS_TEMPLATE_CODE" # <string> serialized json string for sms template parameters. eg. # `'{"alarm_level":"%s","time":"%s","name":"%s","content":"%s"}'` aliSmsTemplateParam: "$SMS_TEMPLATE_PARAM" # <string> phone number list, separated by comma `,` aliSmsPhoneNumbersList: "$SMS_PHONE_NUMBERS" # <string> builtin sms notifier webhook address. aliSmsListenAddr: "$SMS_LISTEN_ADDR" version: 1 # <bool> allow users to edit datasources from the UI. editable: true
-
Now users can quickly import TDinsight dashboard in Dashboards tab in a datasource configuration page.
Monitor TDengine Database with TDengine Data Source Plugin
See How to Monitor TDengine Cluster with Grafana for the details.
TDinsight
TDinsight is a simple monitoring solution for TDengine database. See TDinsight README for the details.
Docker Stack
For a quick look and test, you can use docker-compose
to start a full Grafana + AlertManager + Alert Webhook stack:
docker-compose up -d
Services:
- Grafana: http://localhost:3000
- AlertManager: http://localhost:9093, in docker it's http://alertmanager:9010/sms
- Webhook: http://localhost:9010/sms, in docker it's http://webhook:9010/sms
Dashboards
You can get other dashboards in the examples directory, or search in grafana with TDengine datasource https://grafana.com/grafana/dashboards/?orderBy=downloads&direction=desc&dataSource=tdengine-datasource .
Here is a short list:
- 15146: Multiple TDengines Monitoring Dashboard
- 15155: TDengine Alert Demo
- 15167: TDinsight
- 16388: Telegraf Dashboard with TDengine
You could open a pr to add one if you want to share your dashboard with TDengine community, we appreciate your contribution!