What Is Server Monitoring and What Should You Monitor?
Server monitoring should cover user access, latency, error, CPU, RAM, disk, network, service, database, TLS and backup with Alert and Runbook that can be acted upon.
BIPIDA / IDEAS INTO PRACTICE
Read deeper. Diagnose better. Build with confidence.
Technical analysis and practical experience for your next challenge.
7 articles · Tag: MySQLShowing 1–7
Server monitoring should cover user access, latency, error, CPU, RAM, disk, network, service, database, TLS and backup with Alert and Runbook that can be acted upon.
Design a professional server backup with RPO/RTO, compatible database and file versions, encryption, retention, separation, immutability, monitoring and restore testing.
Recognize Linux Disk overflow with filesystem, inode, directory, log, deleted file open, Docker and database; without rushing to delete production data.
Analyze Linux RAM usage with available, cache, swap, RSS/PSS, process, container and OOM and separate the memory leak from normal memory usage.
To find the cause of the CPU overloading Linux, check the load, user/system/iowait/steal, process, thread, container, PHP and Query in the event timeline.
When the site goes down, check DNS, network, TLS, Nginx, application and database layer by layer, save evidence, and recover the service with the least risk.
Fix 504 by identifying the payment gatewayway builder error, upstream time, PHP row, query database, external API and limit each layer; not increasing arbitrary timeout.