Server Monitoring Basics for Small Business Websites: A Practical Guide

When a UK small business website goes down, the first question is usually "why is the site not loading?" followed quickly by "how do we fix it?" Server monitoring is what gives you the chance to answer those questions before customers notice, rather than scrambling after the damage is done. Without it, a server running out of memory at 2am or a database connection that slowly degrades over days can cost you enquiries, sales, and trust without anyone knowing until the next business day.

This article covers what server monitoring means for small business websites, what you should actually be watching, how to set up basic checks without needing a dedicated operations team, and when it makes sense to ask an IT specialist to take over the monitoring and response.

What server monitoring actually does for a small business website

Server monitoring is the practice of continuously checking whether the server hosting your website is healthy, responsive, and performing within acceptable limits. It includes monitoring server resources like CPU usage, memory consumption, disk space, and load averages, as well as service-level checks such as whether your web server, database, and email services are running correctly.

For a small business, the practical value of monitoring comes down to three things. First, it catches problems early before they become outages. Second, it gives you data to diagnose what went wrong when something does break. Third, it helps you understand whether your hosting setup is adequate for your actual traffic and workload.

A site that loads slowly, crashes occasionally, or serves error pages silently is a site that loses enquiries. For many small UK businesses, even a few hours of unexplained downtime can mean missed quote requests, booking cancellations, or damaged confidence in the brand. Monitoring will not prevent every problem, but it removes the situation where you discover an issue only when a customer emails to say your site is not working.

What you should be monitoring on your web server

Not every metric matters equally for every website. The key is understanding which measurements indicate real problems for your specific setup. Here are the areas that typically matter most for a small business website running on a LAMP stack or similar configuration.

Uptime and HTTP response checks

The most fundamental check is whether your website actually responds to HTTP requests. An uptime monitor sends a request to your domain at regular intervals and alerts you when the site stops responding or returns an unexpected status code such as a 500 error.

Many uptime monitoring services offer free tiers suitable for small business use. You can configure checks from multiple geographic locations to rule out network routing issues. Set the check interval based on how quickly you need to know about an outage. A check every 60 seconds is reasonable for most small business sites.

# Example curl check you can run manually to test response
curl -s -o /dev/null -w "%{http_code}" https://example.com
# Returns HTTP status code: 200 means healthy, 500 means server error

CPU usage and server load

CPU usage tells you how much processing power your server is using. A consistently high CPU load can indicate that your server is underpowered for your traffic, that a script is running inefficiently, or that something malicious like a brute-force attack or cryptominer is consuming resources.

On a Linux server, you can check current load using the uptime command or top for a real-time breakdown by process. The load average shown by uptime represents the average number of processes waiting for CPU time over the last 1, 5, and 15 minutes.

# Check server load and uptime
uptime

# Check CPU and memory usage per process
top -bn1 | head -20

For a small business site on shared hosting, you may not have direct access to these commands, but your hosting control panel usually shows resource usage graphs. On VPS or dedicated servers, having SSH access and knowing how to read these outputs gives you much more diagnostic capability.

Memory usage

Memory exhaustion is a common cause of slow performance and crashes, particularly for WordPress sites or custom PHP applications. When a server runs out of RAM, it often starts using swap space on disk, which is significantly slower and can cause severe performance degradation.

PHP-FPM, MySQL, and the web server itself all consume memory. A memory leak in a poorly written plugin or custom script can gradually consume available RAM until the server becomes unresponsive. Monitoring memory usage over time helps you spot gradual increases before they cause an outage.

# Check memory usage on Linux
free -m

# Shows total, used, free, and swap memory in megabytes

Disk space and inode usage

Running out of disk space causes all sorts of problems: databases cannot write logs, backups fail, and the web server may stop serving pages entirely. Inode exhaustion is less commonly checked but equally important on Linux systems. Inodes are metadata structures that track files on the filesystem, and running out of inodes stops new file creation even if disk space remains available.

# Check disk space
df -h

# Check inode usage
df -i

Common causes of disk space issues include accumulating log files, large backup archives, unpruned email queues, and temporary files left behind by failed processes. Regular maintenance and log rotation help prevent these from becoming problems.

Database connection and query performance

For websites that rely on MySQL or MariaDB, monitoring database health is important. A database that stops accepting connections will take down your website even if the web server itself is fine. Slow queries that lock tables can degrade site performance progressively until pages stop loading.

If you have database access, checking the process list shows current queries and their status. Long-running queries, particularly those in a "Locked" state, often indicate performance problems that need query optimisation or index review.

# Show current MySQL processes and queries
SHOW FULL PROCESSLIST;

# Check MySQL status variables for errors
SHOW GLOBAL STATUS LIKE 'Aborted%';

SSL certificate expiry

An expired SSL certificate causes browsers to show a security warning and makes visitors distrust your site. While this is not strictly a server health metric, it fits within the monitoring umbrella because expiry causes an immediate service impact.

Set up monitoring to alert you at least 30 days before any SSL certificate on your domain expires. Many hosting providers handle certificate renewal automatically through Let's Encrypt, but if you use a manually renewed certificate, missing the expiry date is an avoidable problem.

DNS resolution

DNS issues can make your site unreachable even when the server itself is perfectly healthy. Monitoring DNS resolution from multiple locations helps confirm whether the problem is with your server or with how visitors are reaching it.

A simple check is to use dig or nslookup to verify that your domain resolves to the correct IP address. If DNS resolution fails or points to the wrong address, your site will be unreachable for everyone whose DNS resolver caches the incorrect record.

# Check DNS resolution for your domain
dig example.com

# Check DNS propagation from Google's resolver
dig @8.8.8.8 example.com

How to set up basic server monitoring without expensive tools

Small businesses do not need enterprise-grade monitoring infrastructure to get meaningful visibility into their server health. Several free or low-cost approaches provide useful coverage without significant ongoing cost.

Uptime monitoring services

Services such as UptimeRobot, HetrixTools, and Pingdom offer free or inexpensive monitoring that checks your site from multiple locations and sends alerts by email or SMS when the site stops responding. You configure the check URL, the interval, and the notification contacts. This handles the most critical monitoring for a small business website without requiring any server-side configuration.

The main limitation of external uptime monitoring is that it only tells you whether your site responds to HTTP requests. It will not catch performance degradation, memory leaks, or service-specific problems that do not cause an outright outage.

Server-side monitoring with system tools

If you have a VPS or dedicated server with SSH access, you can set up lightweight monitoring using standard Linux tools. A simple shell script run via cron can log key metrics to a file and alert you if values exceed thresholds.

# Example cron entry to run a monitoring script every 5 minutes
*/5 * * * * /path/to/monitoring-script.sh >> /var/log/server-health.log 2>&1

The monitoring script can check disk space, memory usage, service status, and other metrics, writing results to a log file that you review periodically. If a threshold is exceeded, the script sends an alert via email. This approach requires some Linux familiarity but is straightforward to implement for basic health checks.

Hosting provider monitoring tools

If you use shared hosting or a managed service, your hosting provider typically offers some level of resource monitoring through their control panel. cPanel, Plesk, and similar panels show CPU usage, disk space, bandwidth, and sometimes database metrics.

These tools are useful but limited. They usually show current values and recent history but do not provide custom alerting or long-term trend analysis. Treat them as supplementary to dedicated monitoring rather than your primary visibility tool.

Common server monitoring mistakes that small businesses make

Setting up monitoring is easy. Setting it up in a way that actually helps when something goes wrong is harder. Several common mistakes reduce the usefulness of monitoring or create false confidence.

Monitoring the wrong metrics

Tracking dozens of metrics that never indicate real problems is noise. Focus on the measurements that actually tell you whether your site is healthy and fast. Uptime, response time, disk space, and memory usage cover most of what matters for a typical small business website.

Alert fatigue from overly sensitive thresholds

If your alerts trigger every time CPU usage briefly spikes above 80%, you will start ignoring them or turning them off. Set thresholds that reflect genuine problems rather than normal variation. A CPU spike that lasts 10 seconds during a traffic burst is not worth waking someone up over.

No alerting escalation path

An alert that goes to an unmonitored email address is useless. Define who receives alerts, how they are contacted, and what happens if the first contact does not respond. For a small business without 24-hour staff, this might mean setting up SMS alerts to a phone that is actually checked outside business hours when critical issues arise.

No response plan for alerts

Knowing something is wrong is only useful if you know what to do next. Document the common failure scenarios and basic remediation steps. For example, a disk space alert might require identifying and removing large log files, clearing old backups, or adding disk space to the server. Having this documented means you can act quickly without having to research from scratch during an incident.

Forgetting to test monitoring itself

Monitoring systems can fail. If your uptime monitor goes down or loses connectivity, you will not know your site is offline until a customer tells you. Periodically verify that monitoring is actually working by intentionally triggering an alert or checking that recent monitoring data is being received.

Reading server logs for diagnosis

When monitoring flags an issue, server logs are usually where you find the cause. Understanding what to look for in logs is one of the most practically useful skills for anyone managing a small business website.

Web server logs, typically Apache's access and error logs or Nginx's equivalent, record every request made to your site and any errors the server encountered. Error logs are particularly valuable for diagnosing 500 errors, PHP fatal errors, and other server-side issues.

# Common log locations on Linux servers
# Apache
/var/log/apache2/error.log
/var/log/httpd/error_log

# Nginx
/var/log/nginx/error.log

# MySQL/MariaDB
/var/log/mysql/error.log

When something breaks, the error log often shows the specific PHP fatal error, database connection failure, or permission problem that caused it. Look for entries timestamped around when the issue started. The log may show the same error repeating multiple times before the service eventually failed.

PHP error logs

PHP errors do not always appear in web server error logs depending on your configuration. If PHP displays errors to the browser, it may log nothing server-side. For production sites, disable browser error display and ensure PHP logs errors to a file so they are available for diagnosis.

# Check PHP error log location
php -i | grep error_log

# Common location
/var/log/php-fpm/www-error.log

A custom PHP application or a poorly written WordPress plugin often produces warnings and notices that are ignored in normal operation but become significant under certain conditions such as high traffic or specific request types. Reviewing PHP error logs regularly helps catch these before they escalate.

Server monitoring and website security

Monitoring overlaps with security in several practical ways. A sudden spike in CPU usage might indicate a brute-force attack or a compromised script running malicious code. Unexpected processes, unfamiliar files in your web directory, or unusual outbound traffic can all be detected through server monitoring.

For small businesses, combining basic monitoring with periodic security checks provides reasonable coverage. A practical approach includes regular monitoring of server resources and uptime, periodic review of server logs for suspicious activity, keeping software and PHP versions up to date, and running occasional security scans to identify vulnerabilities.

For more detailed guidance on securing your hosting environment, the shared hosting security checks guide covers file permissions, PHP version management, malware scanning, and other practical steps that complement monitoring.

When to set up server monitoring yourself and when to get help

For a small business running a straightforward website on quality shared hosting, basic external uptime monitoring is often sufficient. If your site is running well, you have not experienced frequent outages, and your hosting provider manages server-level health, you probably do not need elaborate monitoring infrastructure.

Consider investing more in monitoring when your site becomes business-critical, you run a custom application with specific performance requirements, you have experienced unexplained downtime or performance issues in the past, your hosting provider does not offer adequate visibility into server health, or you are planning for growth and need to understand when your current setup will need to scale.

If you do not have the technical comfort to set up monitoring, interpret server logs, or respond to alerts, asking for help is a practical choice. A freelance IT specialist with server management experience can set up appropriate monitoring for your setup and provide a response plan that works for your business availability.

What server monitoring costs in the UK small business context

Monitoring costs range from free to significant, depending on what you need. Basic uptime monitoring services offer free tiers that are adequate for most small business websites. More comprehensive monitoring platforms with advanced features, longer data retention, and SMS alerting typically cost between a few pounds and a few tens of pounds per month.

If you use a managed VPS or dedicated server, your hosting provider may include some monitoring as part of the service. Dedicated server monitoring and alerting solutions from providers like Datadog, New Relic, or similar platforms become relevant when your infrastructure grows beyond basic shared hosting.

The real cost to consider is not just the monitoring tool but the time required to respond to alerts and maintain the setup. For a busy small business owner, the opportunity cost of monitoring and managing server health may exceed the price of professional support.

Monitoring is more useful when the hosting setup itself is healthy. The guide to common hosting mistakes that hurt small business websites covers the configuration issues that often cause the alerts in the first place.