Host resources
CPU, memory, load and filesystem graphs help put a resource problem in context. Explore Linux server monitoring for the server-wide metrics and their history.
Server monitoring puts resource graphs and availability checks in context, with alerts by email, Slack, Telegram or webhook. Connect Linux hosts with one command, review CPU, memory, disk and network measurements, and choose checks for the services people depend on.
Built for developers, sysadmins and small teams running Linux hosts, CloudStats helps investigate resource pressure and availability. A busy graph is a starting point, not a diagnosis: use the server monitoring dashboard to see what changed, then follow the check that matches the problem.
CPU, memory, load and filesystem graphs help put a resource problem in context. Explore Linux server monitoring for the server-wide metrics and their history.
A reporting agent answers a different question from a successful connection to a service. Read about uptime monitoring to distinguish host availability from the checks around it.
An ICMP response and an accepting TCP port are different observations. Choose ping and port monitoring for the external-check topic rather than assuming an open port proves application health.
An online host does not prove that its backup or report completed. Explore cron job monitoring for scheduled tasks and the common reasons they fail silently.
Thresholds with a duration help distinguish sustained problems from brief spikes. Explore server alerts for rule examples and the notification workflow.
HTTP(S) availability and certificate expiry address different ways a site can become unavailable. Start with website monitoring and follow the dedicated guides for each check.
Choose the guide for VPS and dedicated servers, Linux hosts running cPanel/WHM, or Docker hosts. The host resource view does not imply individual-container metrics or a cPanel-specific integration. See all platforms.
1. Install the agent using the one-line command provided during setup.
2. Connect the host and review CPU, memory, load, filesystem utilization, network receive rate and disk read rate.
3. Set alert thresholds and durations, then choose the notification destination appropriate to the problem.
Choose email, Slack, Telegram or webhook instead of making someone watch graphs continuously. Thresholds with a duration keep a short spike separate from a sustained condition. See notification channels for the channel overview; availability depends on your plan.
While CloudStats is getting started, the published plan is Free at $0 per month, with unlimited servers, email alerts and community support. See pricing for the current offer and limits.
FAQ
It is the ongoing observation of a machine's resources and availability so you can investigate changes before they become larger problems. A host reporting through its agent, a reachable port and a successful HTTP response answer different questions. Read those signals together rather than treating one healthy result as proof that everything works.
CloudStats shows CPU, memory, 1-minute load average, filesystem utilization, network receive rate and disk read rate. These are server-wide measurements, not individual-process or individual-container statistics. Use them to understand resource pressure on a host, then choose an availability check appropriate to the service you want to observe.
Yes. While CloudStats is getting started, the published plan is Free at $0 per month, with unlimited servers, email alerts and community support. See the Pricing page for the current offer.
For host resource graphs, install the CloudStats agent on your Linux server using the one-line command provided during setup. After connecting the host, review its metrics and configure the alerts you need. Monitoring a Docker host or a machine running cPanel means observing that Linux host; it does not add container-level or cPanel-account statistics.