Table of contents
3, Docker Department Uptime Kuma
1 Introduction
When using Docker to deploy projects, we need to always know the status of the deployed containers. And usually all site monitoring is configured on the cloud platform to detect the connectivity of each site. Uptime Kuma is an open source monitoring tool that also supports the push of alarm information. In the project I am in now, I use this as a tool for site health status monitoring.
2. What is Uptime Kuma?
Github address: https://github.com/louislam/uptime-kuma
Online experience Demo address: Uptime Kuma Demo
Uptime Kuma is an open source project, developed and maintained by a community of contributors on GitHub. The project was initiated by Muhammad Mustadi, a software engineer from Indonesia who created the initial version of Uptime Kuma in 2019.
The main function:
- Support monitoring the uptime of HTTP(s) / TCP / HTTP(s) Keyword / HTTP(s) Json Query / Ping / DNS Record / Push / Steam Game Server / Docker Containers
- Support Telegram, Discord, Gotify, Slack, Pushover, email (SMTP) and more than 90 notification services to send notifications
- Minimum interval 20S
- ......
3, Docker Department Uptime Kuma
3.1. Installation
The default port is 3001, and only one command is needed to complete the startup installation. It is best to create your own data disk directory here, and hang the configuration information locally on our host machine, otherwise all monitoring information will need to be reconfigured after the container is recreated.
docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1
You can view the containers we are currently creating by command:
docker ps
3.2. Access
Then you can directly access our console address: http://IP:3001. You can see the console page:
Enter the account password to log in to the home page.
3.3. Configuration
Click to add a monitoring item and select our appropriate monitoring type. Here I choose to use the http method.
Then click Set Notification on the right and select the type of notification. Here I choose Feishu Robot Notification:
3.4. Integrated Feishu robot
Add a robot to the Feishu group, and you can view the documents added by Feishu. After adding the robot, you will get a hook address:
Fill in the webhook address into uptime kuma.
After saving, we get our site monitoring information.
3.5. Effect
The following are the site monitoring items configured in my real project. You can see that each monitoring item has some small green marks, which indicate that the current service or site is available. But when unavailable, a red dot will be displayed. And it will trigger the Feishu robot message push we configured earlier.
When an alarm message push is triggered:
We can also choose different alarm notification types, and we can specify different alarm strategies based on our actual situation.