What’s Changed
- feat: monitor the Elasticsearch source card query conditions of the large market support sortBy configuration
- refactor: Added a large disk migration tool page. Starting from ga.4, the global Prometheus cluster switch in the upper right corner has been removed from the large disk details page, and the data source can be switched globally through the data source variable. The new disk migration tool can migrate all the disks in the business group in batches, or migrate them separately on the disk details page
- refactor: Elasticsearch source query index result sorting
- refactor: Subscribe to the alarm rule table column information update of the alarm rule interface
- refactor: optimize the pagination style of all tables
- refactor: Optimize the typesetting when DingTalk notification is @ #1475 by monchcc
- fix: Fix the problem that an error will be reported when filling in the value of the textbox variable in the market
- fix: Fix the time display error of the line graph rendered by Elasticsearch source query time series value
- fix: Fix the problem that if the original value of the Elasticsearch source query log returns an empty object structure data, an error will be reported
- fix: Fix the problem that the business group cannot be edited after the team associated with the business group is deleted
- fix: Tokens processing issue when sending Mattermost messages #1476 by lwangrabbit
- fix: pub static file routing
- fix: When the data source is updated, the status is reset
Introduction to Nightingale
- Nightingale focuses on alarm management. A set of rules automatically takes effect to multiple clusters. Flexible alarm rules, shielding rules, subscription rules, and permission control can be seamlessly integrated with Prometheus, VictoriaMetrics, etc.
- We are trying to develop from a monitoring system to an observation platform, introducing metrics, logging, and tracing data source management, striving to truly be all-in-one in the future, and achieve a good data connection
- The Nightingale project has a total of 95 contributors, 6000+ stargazers, 100+ releases, github address: github.com/ccfos/nightingale
component installation
The installation of Nightingale depends on mysql and redis. These two components are open source software. Please install them yourself. Here is also a small script to install these two components. You can refer to:
# install mysql
yum -y install mariadb*
systemctl enable mariadb
systemctl restart mariadb
mysql -e "SET PASSWORD FOR 'root'@'localhost' = PASSWORD('1234');"
# install redis
yum install -y redis
systemctl enable redis
systemctl restart redis
In the above example, the root password of mysql is set to 1234. It is recommended to keep this unchanged, so as to save the trouble of modifying the configuration file later.
install nightingale
mkdir -p /opt/n9e && cd /opt/n9e
# 去 https://github.com/ccfos/nightingale/releases 找最新版本的包，文档里的包地址可能已经不是最新的了
tarball=n9e-v6.0.0-ga.4.0.1-linux-amd64.tar.gz
urlpath=https://download.flashcat.cloud/${tarball}
wget $urlpath || exit 1
tar zxvf ${tarball}
mysql -uroot -p1234 < n9e.sql
nohup ./n9e &> n9e.log &
# check logs
# check port
If the startup is successful, n9e will listen on port 17000 by default. The above is a simple demonstration using nohup, and it is recommended to use systemd hosting for the production environment. Tutorial on the use of nohup and systemd
The configuration file contains the connection address configuration of mysql. If an error is reported when connecting to the database, you can check the user name and password. etc/config.toml
After the Nightingale server is deployed, the browser can access 17000 to experience related functions. The default user is , and the password is . Configure the corresponding data source, and you can view the data of metrics, logs, and traces on the Nightingale platform. root root.2020
categraf docking v6
categraf docking version v6 needs to be upgraded to version 0.2.35, and the heartbeat switch in the configuration file config.toml should be turned on
v5 upgrade v6 steps
-
Before operation, remember to backup the database!
-
You need to update the Nightingale data source table structure you are using to be consistent with v5.15.0. The release page has update instructions for each version of the table structure. You can follow the instructions to update the table structure one by one according to the version you are using. statement
-
Unzip the n9e installation package, import upgrade.sql to the n9e_v5 database
mysql -h 127.0.0.1 -u root -p1234 < cli/upgrade/upgrade.sql
- Execute n9e-cli to complete the database table structure upgrade, webapi.conf is the configuration file being used by n9e-webapi of v5 version
./n9e-cli --upgrade --config webapi.conf
- Modify the database in the n9e configuration file to n9e_v5, start the n9e process
nohup ./n9e &> n9e.log &
- The port n9e listens to is 17000, and the previous web port and the port for data reporting need to be adjusted to 17000