Docker自带的监控命令
docker top
[root@docker01 ~]# docker top wp_wordpress_1
UID PID PPID C STIME TTY TIME CMD
root 42176 42139 0 18:51 ? 00:00:00 apache2 -DFOREGROUND
33 42610 42176 0 18:51 ? 00:00:00 apache2 -DFOREGROUND
33 42611 42176 0 18:51 ? 00:00:00 apache2 -DFOREGROUND
33 42612 42176 0 18:51 ? 00:00:00 apache2 -DFOREGROUND
33 42613 42176 0 18:51 ? 00:00:00 apache2 -DFOREGROUND
33 42635 42176 0 18:52 ? 00:00:00 apache2 -DFOREGROUND
33 42636 42176 0 18:52 ? 00:00:00 apache2 -DFOREGROUND
33 42637 42176 0 18:52 ? 00:00:00 apache2 -DFOREGROUND
33 42638 42176 0 18:52 ? 00:00:00 apache2 -DFOREGROUND
33 42648 42176 0 18:53 ? 00:00:00 apache2 -DFOREGROUND
33 42693 42176 0 18:57 ? 00:00:00 apache2 -DFOREGROUND
docker stats
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
e10c0068386a wp_wordpress_1 0.00% 89.01MiB / 1.781GiB 4.88% 4MB / 4.19MB 0B / 0B 11
PS:默认会显示一个实时变化的列表,展示每个容器的cpu使用率,内存使用量和可用量
docker logs
[root@docker01 ~]# docker logs wp_wordpress_1
WordPress not found in /var/www/html - copying now...
Complete! WordPress has been successfully copied to /var/www/html
[14-Sep-2020 10:51:14 UTC] PHP Warning: mysqli::__construct(): (HY000/2002): Connection refused in Standard input code on line 22
MySQL Connection Error: (2002) Connection refused
MySQL Connection Error: (2002) Connection refused
MySQL Connection Error: (2002) Connection refused
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.19.0.3. Set the 'ServerName' directive globally to suppress this message
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.19.0.3. Set the 'ServerName' directive globally to suppress this message
……
sysdig
轻量级的系统监控程序
[root@docker01 ~]# docker run -it --rm --name sysdig --privileged=true --volume=/var/run/docker.sock:/host/var/run/docker.sock --volume=/dev:/host/dev --volume=/proc:/host/proc:ro --volume=/boot:/host/boot:ro --volume=/lib/modules:/host/lib/modules:ro --volume=/usr:/host/usr:ro sysdig/sysdig
下载插件失败后可以运行下边的命令,重新下载
root@6d37c6f2646e:/# sysdig-probe-loader
下载成功之后,可以运行sysdig命令,查看监控项
root@e1b7bf293e05:/# csysdig
查看监控项
F2Views——>Containers——>Enter
Weave scope
图形化的显示,能够直观的看到容器资源使用情况,便于理解,监控和控制容器
sudo curl -L git.io/scope -o /usr/local/bin/scope
sudo chmod a+x /usr/local/bin/scope
scope launch
scope可以监控单台dockerhost,也可以监控多台的dockerhost,监控效果只需在运行scope launch 本机IP地址 其他IP地址 , 不过需要注意的是如果是多台的dockerhost,在运行前,保证主机名不能冲突,区别主机名
开启 docker02 (监控多台)
docker01:
[root@docker01 ~]# docker rm -f weavescope
weavescope
[root@docker01 ~]# scope launch 192.168.1.128 192.168.1.129
docker02:
sudo curl -L git.io/scope -o /usr/local/bin/scope
sudo chmod a+x /usr/local/bin/scope
scope launch 192.168.1.129 192.168.1.128
PS:注意,此服务会将宿主机的4040端口打开,然后虽然说使用此服务的人员可以访问,但,同样,如果是集群外的其他IP地址,也能够访问此服务,而且scope目前没有关于USER访问限制。所以,想要使用此服务,必须严格管理宿主机的4040端口的访问。而且最好,将默认的端口进行修改。
共有条评论 网友评论