ServerScope: From Uptime Monitoring to a Complete Monitoring Platform

ServerScope is a project I've been working on to make server, website and domain monitoring easier to manage from one central place. Instead of relying on several separate tools to check whether everything is working, the goal is to bring as much useful information as possible into a single platform.

Over time, the project has grown beyond its original scope. ServerScope is no longer focused only on checking whether a server or website is online. It is also becoming a platform that helps identify problems, understand their causes and keep track of what is happening across an infrastructure.

One place to monitor your infrastructure

A major part of ServerScope is bringing information about different components together. This includes servers, websites, domains and SSL certificates.

Knowing that a website is online is useful, but it does not always tell the whole story. A server might be reachable while an important service has stopped working. Similarly, a website might load correctly even though a specific page or API endpoint is returning errors.

That is why the monitoring capabilities have continued to expand. The aim is to provide a more accurate picture of an environment without making the dashboard unnecessarily complicated.

More detailed website monitoring

One of the major additions is page-level monitoring. ServerScope can now monitor individual pages instead of checking only the homepage.

For example, you can monitor a login page, pricing page or API endpoint. Each page can have its own checks and settings, including expected HTTP status codes, maximum response times, redirect destinations and text that must or must not appear.

Response headers can also be checked. This is useful when you want to verify that a security header, such as Strict-Transport-Security, is still present.

ServerScope can also discover pages automatically through robots.txt, XML sitemaps and internal links. Discovered pages are not automatically added to active monitoring. You can review them first and decide which ones should be monitored.

This makes it easier to monitor larger websites without losing track of individual pages.

Smarter incidents and fewer unnecessary alerts

Another important area of development is incident management.

When several components experience problems at the same time, it is not always clear whether they are separate issues or symptoms of the same underlying failure. Receiving multiple alerts for one underlying problem can make troubleshooting more difficult.

ServerScope addresses this by supporting the grouping of related incidents. For example, when a server goes offline, problems affecting websites that depend on that server can appear under the same root incident.

Dependencies between servers, websites and services can be configured to make these relationships clear. ServerScope can also suggest certain relationships, but they are only used after confirmation.

The system does not simply group every outage that happens at the same time. The goal is to show meaningful relationships when there is a reason to believe that incidents are connected.

More visibility into server services

ServerScope has also expanded beyond basic server availability checks.

It supports monitoring services such as Nginx, Apache, MySQL, PostgreSQL, Redis and PHP-FPM. This makes it possible to check whether important components of a server are still running.

The platform distinguishes between a stopped service, an unresponsive monitoring agent and a server that is actually unreachable.

That distinction matters because each situation can require a different response. A single stopped service may be a much more limited problem than a complete server outage.

The monitoring agent is also designed to read system information without executing remote commands on the server.

Predictive alerts and capacity forecasts

One of the more interesting additions is the ability to identify unusual behaviour and estimate future capacity problems.

ServerScope can analyse historical measurements for CPU usage, memory, swap, system load, network traffic, disk growth, response times and error rates.

For example, if a disk is steadily filling up, the platform can estimate when it may run out of space if the current trend continues.

These forecasts need to be treated carefully. A prediction based on too little data is not particularly useful, so the available history and confidence of the forecast are taken into account.

The objective is to identify potential problems early enough to give you time to respond before they affect the availability of your services.

Better reporting and historical data

Monitoring becomes more useful when you can look back at previous events and understand how your infrastructure has behaved over time.

ServerScope's reporting capabilities include availability, detection times, incident durations and recurring problems. Incident data can also be exported, while reports can be printed or saved as PDFs.

Certificate history provides another useful source of information. You can review certificates previously observed for a domain, including their issuers and validity periods.

Historical data from page checks and forecasts can also be cleaned up according to configured retention periods.

These features make it easier to investigate recurring problems and understand changes in the environment.

The technology behind the platform

Developing ServerScope is not just about adding features. It is also about making sure that the different components work together reliably.

The API has been expanded with endpoints for page monitoring, automatic page discovery, dependencies, services, forecasts and incident management. Write requests also support Idempotency-Key, helping prevent repeated requests from executing the same action more than once.

The health of ServerScope itself is important as well. The system status page helps verify whether scheduled tasks are running, queues are being processed and notifications are being delivered.

Security is another consideration, particularly because the platform automatically makes requests to external websites. Internal, local and cloud metadata addresses are blocked during checks, including when redirects are followed.

These protections are important for a platform that regularly interacts with external services.

What's next?

ServerScope now offers considerably more than a basic uptime checker. It combines server and website monitoring with incident management, historical data and reporting.

There is still plenty of room for improvement. One of the main priorities is making sure that all these features work together reliably and that the information provided by the platform genuinely helps when troubleshooting problems.

The long-term goal is to build a platform that does more than tell you something has gone wrong. It should also help you understand where to look and what needs attention.

Ultimately, it comes down to three things: detecting problems earlier, reducing unnecessary alerts and giving you more control over your infrastructure.