Deploy the V3 version of the open source Nightingale operation and maintenance monitoring platform

Official address

https://github.com/didi/nightingale

The nightingale operation and maintenance platform is an open source operation and maintenance platform of Didi with the best practices of the Didi company
.
用户资源中心（RDB）、
资产管理系统（AMS）、
任务执行中心（JOB）
监控告警系统（MON）

For details, please see the official website. Here we will focus on the deployment steps

The docker deployment I used here

The first step github pulls the code mirror to the specified location of the server

You can also go to http://116.85.64.82/ to pull the latest version of the tar package

The pull is completed as shown in the figure

The second step is to configure startup items

Download docker-compose

curl -L https://github.com/docker/compose/releases/download/1.25.0-rc4/docker-compose-`uname -s`-`uname -m` -o /usr/local/bin/docker-compose
chmod  +x  /usr/local/bin/docker-compose

Use docker-compose to download, generate and start the image

cd    /home/yeying-master/nightingale-master/dockerfiles
docker-compose up    #启动

After startup, docker ps will generate four containers as shown in the figure

Pay attention to the port not to be occupied, otherwise it will not start normally

If there is no error, you can access normally

The initial account password is root root. At this point in 2020, the master node is built

The third step is to configure the node node

 wget http://116.85.64.82/n9e.tar.gz
tar  -xf   n9e.tar.gz

After decompression as shown

[root@yeyin-master ~]# ll
-rwxr-xr-x. 1 root root     3065 10月  9 23:02 control
drwxr-xr-x. 4 root root     4096 10月  9 23:03 etc
-rwxr-xr-x. 1 root root 22834094 10月  8 19:50 n9e-agent
-rwxr-xr-x. 1 root root 20181862 10月  8 19:50 n9e-ams
-rwxr-xr-x. 1 root root 22098532 10月  8 19:50 n9e-index
-rwxr-xr-x. 1 root root 20610070 10月  8 19:50 n9e-job
-rwxr-xr-x. 1 root root 22062651 10月  8 19:50 n9e-judge
-rwxr-xr-x. 1 root root 22890758 10月  8 19:49 n9e-monapi
-rwxr-xr-x. 1 root root 23874802 10月  9 22:49 n9e-rdb
-rw-r--r--. 1 root root 97333889 10月  9 23:03 n9e.tar.gz
-rwxr-xr-x. 1 root root 23887629 10月  8 19:50 n9e-transfer
-rwxr-xr-x. 1 root root 20424816 10月  8 19:50 n9e-tsdb
drwxr-xr-x. 2 root root      101 9月  28 10:07 sql

Package and copy control n9e-agent /etc/address.yml /etc/agent.yml /etc/identity.yml to /home/n9e/

as the picture shows

Modify the configuration file vim address.yml to change the global 192.168.106.132 to the host ip of the master node

 :%s/192.168.106.132/ip/g

Configure boot service

vim     /usr/lib/systemd/system/agent.service
Description=n9e agent
After=network-online.target
Wants=network-online.target

[Service]
# modify when  deploy  in prod env
User=root
Group=root

Type=simple
Environment="GIN_MODE=release"
ExecStart=/home/n9e/n9e-agent
WorkingDirectory=/home/n9e

Restart=always
RestartSec=1
StartLimitInterval=0

[Install]
WantedBy=multi-user.target

systemctl restart agent
systemctl enable agent
check that no error is reported, indicating that the startup is normal
systemctl status agent

Enter the web platform

You can see the host information of the node node just added

Task execution center can execute tasks in batches

User center can join the server in batches

The monitoring market can produce the corresponding server monitoring content, which is quite intuitive