Have you ever received a notification that the server "collapsed" in the middle of the night, but then spent hours straining to find out what the hell was going on inside? I have experienced this countless times in the first years of my career. Instead of being passive, in this article I will share the "unbeatable" combo that I am using: combining monitoring server Uptime Kuma Netdata. This is a comprehensive, open source observability solution that helps you know exactly WHEN the server crashes and WHY it crashes, especially with extremely smooth installation in just 5 minutes with Docker.
Uptime Kuma & Netdata: The Perfect Couple for Observability - One "Gatekeeper", One "Endoscopy Doctor"
The combination of Uptime Kuma and Netdata provides a comprehensive monitoring solution, in which Uptime Kuma monitors external status (black-box), while Netdata deeply analyzes internal performance (white-box).
So what exactly is Observability in server monitoring? Unlike traditional monitoring that only tells you that the system is failing, observability helps you understand the internal state of the system based on output data. For system administrators or DevOps engineers, just knowing the web is inaccessible is not enough. You need to know exactly which service died, whether it was due to running out of RAM or due to network congestion.
Equipping system monitoring skills is a mandatory step. If you are a programmer who wants to get into the system field, mastering Basic Linux server administration for developers is the solid foundation to start approaching these concepts. Once you understand Linux, server monitoring with Uptime Kuma Netdata will become extremely intuitive.
Uptime Kuma's role: "Gatekeeper" warns from the outside (Black-box Monitoring)
Uptime Kuma acts as a gatekeeper, continuously checking services via HTTP(s), TCP, Ping and DNS to instantly detect downtime.
This is a great self-hosted tool with an intuitive interface. Instead of paying for external services like UptimeRobot, you can completely host Uptime Kuma yourself. According to the latest updates as of early 2026 (version 2.0+), Uptime Kuma has support for MariaDB for large systems and the ability to run Docker without root permissions, enhancing maximum security.
This tool continuously "knocks" on your server using protocols such as HTTP(s), TCP, Ping, DNS to see if the service is alive. It even tracks the expiration date of the SSL certificate. As soon as there is a change, the notification system (Telegram, Discord, Email) will ring your name immediately.
Netdata's role: "Endoscopy doctor" diagnoses from the inside (White-box Monitoring)
Netdata collects thousands of metrics every second, providing detailed insight into CPU, RAM, Disk and network systems to help identify the root cause of problems.
If Uptime Kuma reports a website crash, Netdata will answer the question "Why?". Server performance monitoring with Netdata delivers an extremely impressive out-of-the-box experience. Netdata v2.8 updates (late 2025 - early 2026) have strongly integrated AI-powered root cause analysis (AI root cause analysis) and anomaly detection (anomaly detection), making logs and metrics easier than ever.
Netdata delves into every corner of the operating system, providing real-time monitoring of hardware resource consumption. To optimize resource monitoring (CPU, RAM, Disk), you also need to clearly understand the infrastructure platform you are using. If you are still wondering about hardware power, the article Shared hosting vs VPS vs Dedicated will help you have a clearer view of the resource limits of each type of server.
Deploy an Entire System in 5 Minutes with Docker Compose
Simultaneous deployment of Uptime Kuma and Netdata becomes extremely simple and consistent through a single docker-compose.yml file.
Both of these tools are open source and support Docker perfectly. Below are instructions for installing Uptime Kuma Docker combined with Netdata that at Pham Hai, I often apply to small and medium projects.
Step 1: Prepare the docker-compose.yml file for both Uptime Kuma and Netdata
Create a Docker Compose configuration file that defines both the Uptime Kuma and Netdata services along with the volumes needed to store the data.
Bạn chỉ cần tạo một thư mục, ví dụ monitoring, và tạo file docker-compose.yml với nội dung cơ bản như sau:
version: '3.8'
services:
uptime-kuma:
image: louislam/uptime-kuma:1
container_name: uptime-kuma
volumes:
- ./uptime-kuma-data:/app/data
ports:
- "3001:3001"
restart: unless-stopped
netdata:
image: netdata/netdata:latest
container_name: netdata
pid: host
network_mode: host
restart: unless-stopped
cap_add:
- SYS_PTRACE
- DAC_READ_SEARCH
- SYS_ADMIN
volumes:
- netdataconfig:/etc/netdata
- netdatalib:/var/lib/netdata
- netdatacache:/var/cache/netdata
- /etc/passwd:/host/etc/passwd:ro
- /etc/group:/host/etc/group:ro
- /proc:/host/proc:ro
- /sys:/host/sys:ro
- /etc/os-release:/host/etc/os-release:ro
volumes:
netdataconfig:
netdatalib:
netdatacache:
Sau khi lưu file, chạy lệnh docker compose up -d. Chỉ mất vài phút để hệ thống kéo image về và khởi chạy. Thường thì mình sẽ dùng thêm Nginx Proxy Manager để gán domain và HTTPS cho các port này. Nếu bạn đang quản lý nhiều dịch vụ trên cùng một máy chủ, việc tham khảo cách Tự setup VPS chạy nhiều website sẽ hướng dẫn chi tiết cách dùng reverse proxy để định tuyến traffic an toàn.
Step 2: Configure Uptime Kuma - Add the first monitor to monitor the service
Access the Kuma Uptime interface at port 3001, create an account and set up HTTP or Ping monitors to monitor important endpoints.
Ngay khi truy cập http://<IP-Server>:3001, bạn tạo tài khoản admin. Việc tiếp theo là thêm Monitor. Chọn kiểu giám sát (HTTP(s) là phổ biến nhất), nhập URL website hoặc API của bạn.
Cách giám sát Docker container với Uptime Kuma cũng rất đơn giản. Bạn có thể trỏ URL về chính IP nội bộ của container mạng Docker để kiểm tra xem service bên trong có phản hồi hay không. Đừng quên tạo một status page công khai để team hoặc khách hàng có thể theo dõi tình trạng hệ thống mạng và dịch vụ.
Step 3: Explore the server's "internals" with Netdata's real-time dashboard
Open Netdata via port 19999 to instantly see real-time graphs of resource consumption without complicated configuration.
Truy cập http://<IP-Server>:19999, bạn sẽ bị choáng ngợp (theo nghĩa tích cực) bởi số lượng biểu đồ mà Netdata tự động tạo ra. Không cần viết query phức tạp, mọi thứ từ CPU, RAM, Disk I/O cho đến số lượng kết nối mạng đều hiển thị realtime với độ trễ chỉ tính bằng mili-giây.
Real Scenario: From Alert "API Not Responding" To Finding The Error Culprit
When problems occur, the standard procedure is to receive warnings from Uptime Kuma, then use Netdata to trace the process or container causing the overload.
Imagine at 2am, your infrastructure has problems. How todetermine the root cause fastest? This is where how to combine Uptime Kuma and Netdata comes into play.
Set up Kuma Uptime alerts on Telegram/Discord: Receive news as soon as there is an incident
Configure Webhook or Bot API in Uptime Kuma to push notifications directly to your phone via Telegram or Discord as soon as the service is interrupted.
In the Settings section of Uptime Kuma, go to the Notifications section. Kuma Netdata Uptime alert configuration is very flexible. I usually set up a Telegram bot. When the API returned error code 502 (Bad Gateway), Uptime Kuma immediately shot the message: "🔴 DOWN: API Service is having trouble".
Workflow for troubleshooting: Alert from Uptime Kuma -> Open Netdata -> Immediately see which process is "eating" CPU
The processing process starts from Uptime Kuma's website crash notice, the administrator immediately opens Netdata to scan the CPU and RAM graphs to find the error process.
Nhận được alerts, mình không cần SSH ngay vào server để gõ lệnh top hay htop. Mình mở thẳng URL của Netdata. Đập vào mắt là biểu đồ CPU đang dựng đứng ở mức 100%. Cuộn xuống phần "Applications", mình thấy ngay tiến trình node của container API đang bị kẹt vòng lặp vô hạn (infinite loop) gây ngốn tài nguyên. Đôi khi, nguyên nhân là do lượng truy cập tăng đột biến. Trong những trường hợp đó, giải pháp lâu dài là phải tính đến việc Auto scaling VPS khi traffic tăng đột biến để hệ thống tự động mở rộng tài nguyên.
Actual benefits: Reduce downtime, identify root cause quickly
This combination helps minimize MTTR (Mean Time To Recovery) time, ensuring the server always operates stably and optimizes performance.
Lợi ích khi dùng Uptime Kuma và Netdata chính là rút ngắn thời gian "mò mẫm". Bạn có cảnh báo tức thời, bạn có dữ liệu độ phân giải cao. Điều này đặc biệt hữu ích cho các home lab enthusiasts (người đam mê hệ thống cá nhân) muốn có một hệ thống Enterprise-grade nhưng chi phí bằng 0.
Expand & Compare: Why Is This Combo Effective?
Compared to other cumbersome solutions, the Uptime Kuma and Netdata combo delivers the perfect balance between ease of use, zero cost, and deep visibility.
The market for open source server monitoring solutions is huge. Before deciding on a tool, you also need to evaluate what platform your current infrastructure is running on. Understanding How VPS vs Cloud hosting is different will help you choose a method to deploy these monitoring tools that is least affected by physical hardware errors.
Uptime Kuma + Netdata vs. Prometheus + Grafana: The battle between "Simple" and "Flexibility"
While Prometheus and Grafana offer endless customization capabilities but require complex configuration, Uptime Kuma and Netdata score perfect points thanks to their "out-of-the-box" capabilities.
When it comes to monitoring, everyone thinks of Prometheus and Grafana, or older tools like Zabbix, Nagios.
- Prometheus/Grafana: Tuyệt vời cho Kubernetes và các hệ thống microservices khổng lồ. Tuy nhiên, đường cong học tập (learning curve) rất dốc. Bạn phải tự viết PromQL, tự build dashboard.
- Uptime Kuma/Netdata: Cài xong là chạy. Không cần viết một dòng query nào. Phù hợp cho 80% nhu cầu của các doanh nghiệp vừa và nhỏ (SME) muốn tối ưu hóa hiệu suất mà không cần nuôi một team giám sát riêng.
Compare Uptime Kuma and Netdata: Don't ask which one is better, ask "When to use which one?"
Uptime Kuma cannot replace Netdata and vice versa; Uptime Kuma reports service status, while Netdata provides hardware performance data.
Many of you wonder which one is better Uptime Kuma and Netdata?. Actually, this is the wrong question. Comparing Uptime Kuma and Netdata is like comparing a security camera in front of the house (Uptime Kuma) and a temperature sensor system inside the house (Netdata). They complement each other to create a comprehensive surveillance picture.
Integrate into the DevOps ecosystem: Put observability at the heart
Including this monitoring system in operations helps engineering teams proactively detect errors before they affect end users.
Tích hợp Uptime Kuma Netdata cho DevOps mang lại khả năng scalability (mở rộng) rất tốt. Bạn có thể dùng API của Netdata để stream metrics về một database trung tâm khi có nhiều server. Để hệ thống có thể mở rộng mượt mà, việc chọn nhà cung cấp hạ tầng ban đầu cực kỳ quan trọng. Bạn có thể xem qua bài DigitalOcean vs Vultr vs Linode so sánh để có quyết định đầu tư máy chủ hợp lý nhất cho hệ sinh thái DevOps của mình.
Don't just monitor uptime, really "understand" your system. Combining Uptime Kuma's simplicity in failure alerting and Netdata's deep analytics power delivers a powerful, autonomous, and virtually free observability solution. At Pham Hai, I believe this is an extremely beneficial combo for system administrators, DevOps or homelab lovers, helping us from passive to proactive in infrastructure management.
What tool are you using to monitor the server? Share your favorite combos in the comments so everyone can learn!
Lưu ý: Các thông tin trong bài viết này chỉ mang tính chất tham khảo. Để có được lời khuyên tốt nhất, vui lòng liên hệ trực tiếp với chúng tôi để được tư vấn cụ thể dựa trên nhu cầu thực tế của bạn.
