HelloWorld
登录

云原生之使用docker部署uptime-kuma服务器监控面板

江湖有缘

2023-10-15

987 0 0

一、uptime-kuma介绍

uptime-kuma是一款开源的、多功能的服务器监控面板 。

二、检查docker环境

1.检查docker状态

1[root@jeven ~]# systemctl status docker
2● docker.service - Docker Application Container Engine
3   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
4   Active: active (running) since Fri 2022-12-02 04:34:05 CST; 5 days ago
5     Docs: https://docs.docker.com
6 Main PID: 10004 (dockerd)
7    Tasks: 136
8   Memory: 3.1G
9   CGroup: /system.slice/docker.service
10           ├─  8186 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 8987 -container-ip 172.17.0.3 -container-port 3001
11           ├─  8192 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 8987 -container-ip 172.17.0.3 -container-port 3001
12           ├─ 10004 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
13           ├─ 65292 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 8777 -container-ip 172.17.0.4 -container-port 80
14           ├─ 65298 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 8777 -container-ip 172.17.0.4 -container-port 80
15           ├─117192 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 453 -container-ip 192.168.240.2 -container-port 443
16           ├─117198 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 453 -container-ip 192.168.240.2 -container-port 443
17           ├─117211 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 8161 -container-ip 192.168.240.2 -container-port 81
18           ├─117217 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 8161 -container-ip 192.168.240.2 -container-port 81
19           ├─117229 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 8061 -container-ip 192.168.240.2 -container-port 80
20           ├─117235 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 8061 -container-ip 192.168.240.2 -container-port 80
21           ├─122772 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 443 -container-ip 172.24.0.2 -container-port 443
22           ├─122778 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 443 -container-ip 172.24.0.2 -container-port 443
23           ├─122792 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 8023 -container-ip 172.24.0.2 -container-port 80
24           ├─122797 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 8023 -container-ip 172.24.0.2 -container-port 80
25           ├─125465 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 8133 -container-ip 192.168.16.2 -container-port 80
26           ├─125470 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 8133 -container-ip 192.168.16.2 -container-port 80
27           ├─126264 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 8276 -container-ip 172.17.0.2 -container-port 80
28           └─126270 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 8276 -container-ip 172.17.0.2 -container-port 80
29
30Dec 07 16:07:08 jeven dockerd[10004]: time="2022-12-07T16:07:08.423088936+08:00" level=info msg="Layer sha256:64d536caa03db14629265c6a5553...eaned up"
31Dec 07 16:07:08 jeven dockerd[10004]: time="2022-12-07T16:07:08.504084245+08:00" level=info msg="Layer sha256:64d536caa03db14629265c6a5553...eaned up"
32Dec 07 16:15:28 jeven dockerd[10004]: time="2022-12-07T16:15:28.183055538+08:00" level=info msg="Container failed to exit within 10s of si...124cf8fc2
33Dec 07 16:15:28 jeven dockerd[10004]: time="2022-12-07T16:15:28.230585659+08:00" level=info msg="ignoring event" container=d0fd0c5a50e921c...skDelete"
34Dec 07 16:21:23 jeven dockerd[10004]: time="2022-12-07T16:21:23.742077933+08:00" level=info msg="Container failed to exit within 10s of si...dab894fb5
35Dec 07 16:21:23 jeven dockerd[10004]: time="2022-12-07T16:21:23.797450110+08:00" level=info msg="ignoring event" container=13b4daa70e01805...skDelete"
36Dec 07 22:27:25 jeven dockerd[10004]: time="2022-12-07T22:27:25.797566666+08:00" level=info msg="Pull session cancelled"
37Dec 07 22:27:26 jeven dockerd[10004]: time="2022-12-07T22:27:26.872707017+08:00" level=error msg="Not continuing with pull after error: co...canceled"
38Dec 07 22:30:25 jeven dockerd[10004]: time="2022-12-07T22:30:25.868361013+08:00" level=info msg="ignoring event" container=64f382767f860bd...skDelete"
39Dec 07 22:38:51 jeven dockerd[10004]: time="2022-12-07T22:38:51.981442249+08:00" level=info msg="ignoring event" container=544a3ed21fddcd3...skDelete"
40Hint: Some lines were ellipsized, use -l to show in full.
41[root@jeven ~]#

2.检查docker版本

1[root@jeven kuma]# docker version
2Client: Docker Engine - Community
3 Version:           20.10.17
4 API version:       1.41
5 Go version:        go1.17.11
6 Git commit:        100c701
7 Built:             Mon Jun  6 23:05:12 2022
8 OS/Arch:           linux/amd64
9 Context:           default
10 Experimental:      true
11
12Server: Docker Engine - Community
13 Engine:
14  Version:          20.10.17
15  API version:      1.41 (minimum version 1.12)
16  Go version:       go1.17.11
17  Git commit:       a89b842
18  Built:            Mon Jun  6 23:03:33 2022
19  OS/Arch:          linux/amd64
20  Experimental:     false
21 containerd:
22  Version:          1.6.6
23  GitCommit:        10c12954828e7c7c9b6e0ea9b0c02b01407d3ae1
24 runc:
25  Version:          1.1.2
26  GitCommit:        v1.1.2-0-ga916309
27 docker-init:
28  Version:          0.19.0
29  GitCommit:        de40ad0
30

三、下载uptime-kuma镜像

1[root@jeven kuma]# docker pull louislam/uptime-kuma:1
21: Pulling from louislam/uptime-kuma
31: Pulling from louislam/uptime-kuma
44b7b4a8876e2: Pull complete 
5e05e9bb59438: Pull complete 
6911c1003bc81: Pull complete 
700d25b468f79: Pull complete 
8acbb79e9e26e: Pull complete 
9846ef4780c5d: Pull complete 
10d4ca0209da08: Pull complete 
11a1370fa12225: Pull complete 
125c67314e6b08: Pull complete 
13fcd07c4be961: Pull complete 
14Digest: sha256:a84767d7934f833010b886f3dfc57b9d23ca69e85e48f378b28b5c25c5043e1d
15Status: Downloaded newer image for louislam/uptime-kuma:1
16docker.io/louislam/uptime-kuma:1
17
18
19
20

四、部署uptime-kuma

1.创建数据目录

1[root@jeven ~]# mkdir -p /data/kuma/data
2[root@jeven ~]# cd /data/kuma/
3[root@jeven kuma]#

2.创建uptime-kuma容器

1[root@jeven kuma]# docker run -d --name kuma --restart=always -p 3001:3001 -v /data/kuma/data:/app/data -v /var/run/docker.sock:/var/run/docker.sock  louislam/uptime-kuma:1
209a9c130381326f7b41681fd59e0f6376247a1130fb33aff73505014b86b1c4b
3
4
5

3.查看uptime-kuma容器状态

1[root@jeven kuma]# docker ps
2CONTAINER ID   IMAGE                                   COMMAND                  CREATED         STATUS                            PORTS                                                                                                                 NAMES
309a9c1303813   louislam/uptime-kuma:1                  "/usr/bin/dumb-init …"   8 seconds ago   Up 7 seconds (health: starting)   0.0.0.0:3001->3001/tcp, :::3001->3001/tcp                                                                             kuma
4
5

4.查看uptime-kuma容器日志

1[root@jeven kuma]# docker logs kuma 
2==> Performing startup jobs and maintenance tasks
3==> Starting application with user 0 group 0
4Welcome to Uptime Kuma
5Your Node.js version: 16
62022-12-07T15:27:35.692Z [SERVER] INFO: Welcome to Uptime Kuma
72022-12-07T15:27:35.692Z [SERVER] INFO: Node Env: production
82022-12-07T15:27:35.692Z [SERVER] INFO: Importing Node libraries
92022-12-07T15:27:35.693Z [SERVER] INFO: Importing 3rd-party libraries
102022-12-07T15:27:36.114Z [SERVER] INFO: Creating express and socket.io instance
112022-12-07T15:27:36.115Z [SERVER] INFO: Server Type: HTTP
122022-12-07T15:27:36.116Z [SERVER] INFO: Importing this project modules
132022-12-07T15:27:36.161Z [NOTIFICATION] INFO: Prepare Notification Providers
142022-12-07T15:27:36.202Z [SERVER] INFO: Version: 1.18.5
152022-12-07T15:27:36.289Z [DB] INFO: Data Dir: ./data/
162022-12-07T15:27:36.289Z [SERVER] INFO: Connecting to the Database
172022-12-07T15:27:36.423Z [DB] INFO: SQLite config:
18[ { journal_mode: 'wal' } ]
19[ { cache_size: -12000 } ]
202022-12-07T15:27:36.430Z [DB] INFO: SQLite Version: 3.38.3
212022-12-07T15:27:36.431Z [SERVER] INFO: Connected
222022-12-07T15:27:36.432Z [DB] INFO: Your database version: 10
232022-12-07T15:27:36.432Z [DB] INFO: Latest database version: 10
242022-12-07T15:27:36.432Z [DB] INFO: Database patch not needed
252022-12-07T15:27:36.433Z [DB] INFO: Database Patch 2.0 Process
262022-12-07T15:27:36.446Z [SERVER] INFO: Load JWT secret from database.
272022-12-07T15:27:36.448Z [SERVER] INFO: Adding route
282022-12-07T15:27:36.519Z [SERVER] INFO: Adding socket handler
292022-12-07T15:27:36.519Z [SERVER] INFO: Init the server
302022-12-07T15:27:36.536Z [SERVER] INFO: Listening on 3001
312022-12-07T15:27:36.811Z [AUTH] INFO: Login by token. IP=192.168.3.11
322022-12-07T15:27:36.814Z [AUTH] INFO: Username from JWT: admin
332022-12-07T15:27:36.817Z [AUTH] INFO: Successfully logged in user admin. IP=192.168.3.11
342022-12-07T15:27:37.386Z [MONITOR] WARN: Monitor #2 'docker-status': Failing: Cannot read properties of null (reading '_dockerType') | Interval: 60 seconds | Type: docker | Down Count: 0 | Resend Interval: 0
352022-12-07T15:27:47.833Z [AUTH] INFO: Login by token. IP=192.168.3.11
362022-12-07T15:27:47.833Z [AUTH] INFO: Username from JWT: admin
372022-12-07T15:27:47.835Z [AUTH] INFO: Successfully logged in user admin. IP=192.168.3.11
382022-12-07T15:27:52.058Z [MONITOR] INFO: Get Monitor: 2 User ID: 1
392022-12-07T15:28:09.550Z [MANAGE] INFO: Resume Monitor: 2 User ID: 1
402022-12-07T15:28:09.554Z [MONITOR] WARN: Monitor #2 'docker-status': Failing: Cannot read properties of null (reading '_dockerType') | Interval: 60 seconds | Type: docker | Down Count: 0 | Resend Interval: 0
412022-12-07T15:28:09.564Z [MONITOR] INFO: Get Monitor: 2 User ID: 1
422022-12-07T15:28:37.619Z [MONITOR] INFO: Get Monitor: 2 User ID: 1
432022-12-07T15:28:56.543Z [MANAGE] INFO: Resume Monitor: 2 User ID: 1
442022-12-07T15:28:56.567Z [MONITOR] INFO: Get Monitor: 2 User ID: 1
45
46
47

五、访问uptime-kuma服务

1.创建账号

image.png

2.访问uptime-kuma首页

image.png

六、添加http监控项

1.添加http监控项

image.png

2.查看监控项状态

image.png

七、添加docker监控项

1.配置docker宿主信息

在这里插入图片描述

在这里插入图片描述

2.添加docker监控项

在这里插入图片描述

3.查看监控项状态

在这里插入图片描述

点赞
收藏

评论区

加载中...

相关推荐

Oracle 分组与拼接字符串同时使用

SELECTT.,ROWNUMIDFROM(SELECTT.EMPLID,T.NAME,T.BU,T.REALDEPART,T.FORMATDATE,SUM(T.S0)S0,MAX(UPDATETIME)CREATETIME,LISTAGG(TOCHAR(

4.Grafana展示监控数据

Grafana是什么？我们知道Node\_export监控服务器状态，但是没有具体的展示，简单来说，Grafana的主要作用就是对监控的数据进行图形化展示。docker部署grafana我们这里采用docker方式部署，Docker安装，可参考Centos7下实现dockerwordpress安装(https://

2019 年 CNCF 中国云原生调查报告

!头图.jpg(https://ucc.alicdn.com/pic/developerecology/6db0c465111b4d9a96eb1ffe85c00e7a.jpg)中国72％的受访者生产中使用Kubernetes在CNCF，为更好地了解开源和云原生技术的使用，我们定期调查社区。这是第三次中国云原生调查，以中文进行

1. 容器化部署一套云服务 第一讲 Jenkins（Docker + Jenkins + Yii2 + 云服务器)）

容器化部署一套云服务系列1\.容器化部署一套云服务之Jenkins(https://www.oschina.net/action/GoToLink?urlhttps%3A%2F%2Fwww.cnblogs.com%2Fjackson0714%2Fp%2Fdeploy1.html)一、购买服务器服务器!caeef00

Docker 监控

如今，越来越多的公司开始使用Docker了，2/3的公司在尝试了Docker后最终使用了它。为了能够更精确的分配每个容器能使用的资源，我们想要实时获取容器运行时使用资源的情况，怎样对Docker上的应用进行监控呢？Docker的结构会不会加大监控难度？可是在没有专业运维团队来监控Docker的情况下，并且还想加快Dock

构建一体化云原生安全防御体系，京东云云原生安全平台重磅发布

当用户充分利用原生云能力进行应用设计、部署和运维时，云原生也面临新的安全挑战，例如镜像漏洞与投毒、编排软件漏洞、不安全配置利用、容器逃逸等。面对这样的风险，京东云重磅发布云原生安全平台，包含资产清点、镜像安全、运行时安全、网络安全、集群安全、节点安全等安全