Updates

Changes, new features and improvements, newest first.

1. 30 October 2026

   Connect a server with one command

   You now connect a Linux server with one command, without copying files or filling in tokens by hand.

   New#

   • Servers → Server toevoegen → Linux: create an enrollment token and copy the install command. The token is valid for 60 minutes, works once and can be revoked.
   • The script installs the agent on Ubuntu 22.04+ or Debian 12+ (amd64 or arm64), asks for the enrollment token (hidden input) and waits for the first sample. The page shows live when the server is connected.
   • Running it again is safe: a working installation is only updated, not enrolled a second time.
   • Uninstall with --uninstall: the agent revokes its own access and removes its files. The server and its history stay in ServerScope.

   Security#

   • Only a hash of an enrollment token is stored. Tokens and credentials never end up in logs, the audit log or the script's output.
   • HTTPS only (TLS 1.2+). The agent package is checked with a SHA-256 checksum.
   • The agent never executes commands on request of the server.

   Good to know#

   • The manual installation and all existing agents keep working.
2. 29 October 2026

   Teams and roles

   ServerScope now works with teams. Every customer is a team, and a team only sees its own servers, domains, incidents and settings.

   New#

   • Teams: all your servers, domains, websites, alert rules, incidents, webhooks, status pages, API tokens and the audit log belong to one team. Data of another team is never visible.
   • Roles per team: owner, admin or member. Your role only applies to the team in which you have it.
   • Switching teams: if you are a member of several teams, switch with the team switcher.
   • Members per team: an overview of who is in your team.

   Good to know#

   • All existing data is in one default team. Nothing is lost.
   • An API token belongs to one team and stops working when its owner leaves that team.
   • Existing agents keep working as they did.
3. 28 October 2026

   v0.4.0

   • New Per-Page Website Monitoring Monitor individual website pages and check status codes, response times, page content and security headers
   • New Automatic Page Discovery Discover pages through sitemaps, robots.txt and internal links. Choose which discovered pages you want to monitor.
   • New Smart Incident Grouping Related outages are grouped into a single incident, helping you identify underlying causes faster.
   • New Server Service Monitoring Monitor services such as Nginx, Apache, MySQL, PostgreSQL, Redis and PHP-FPM.
   • New Predictive Alerts Receive warnings about unusual system performance and forecasts showing when disks or memory are at risk of running out.
   • New Website Content Change Tracking See which text has been added or removed from a website and track changes to selected response headers.
   • New System Health Status Check whether the ServerScope scheduler, queue, monitoring checks and notification delivery are functioning correctly.
   • New Extended API New API endpoints for page monitoring, dependencies, services, forecasts and incident management.
   • Improved Enhanced Incident Reporting Incidents now include detection time, recurrence information and relationships with other incidents.
   • Improved Four Severity Levels Alerts are now categorized as Low, Medium, High and Critical.
   • Improved More Reliable Recovery Notifications Configure how many consecutive successful checks are required before an incident is reported as recovered.
   • Improved Expanded Reporting Review availability, detection times, incident durations, recurring problems and incident data exports.
   • Improved Certificate History Review previously observed SSL/TLS certificates, including their issuers and validity periods.
   • Improved Expanded Server Metrics View charts for swap usage, network traffic, disk activity and network errors.
   • Improved Per-Resource Notifications Choose whether to receive notifications for specific servers, domains, website pages or services.
   • Improved Improved Incident Management When manually resolving an incident, you must now briefly describe the cause and the solution.
   • Fixed Reduced Duplicate Incident Notifications Related outages can be grouped under a single root incident. Grouped incidents no longer send separate notifications while the root incident remains active.
   • Fixed More Reliable Recovery Detection Recovery notifications can be delayed until multiple consecutive successful checks have been completed.
   • Fixed Improved Error Classification Website checks distinguish between network errors, timeouts, DNS errors, certificate errors, redirect errors, incorrect status codes and failed content checks.
   • Fixed Enhanced Monitoring Security Internal, local and cloud metadata addresses are blocked during website checks and page discovery, including after redirects.
   • Fixed Prevention of Duplicate API Requests API write requests support Idempotency-Key, preventing repeated requests from unintentionally being executed more than once.
4. 26 October 2026

   Website monitoring, smarter incidents and forecasts

   This update turns ServerScope into more than an uptime monitor. You can now monitor complete websites page by page, related outages are combined into one incident, and ServerScope warns you in advance when a disk is about to fill up. All existing monitoring, history and integrations keep working as before.

   New#

   Per-page monitoring

   • Monitor more than the homepage: add pages such as /pricing, /login or /api/health. Each page has its own interval, thresholds, notifications and history.
   • Per page you can check the status code, maximum response time, the final address after redirects, text that must or must not appear, and response headers (for example Strict-Transport-Security).
   • ServerScope tells apart a network error, a time-out, a DNS error, a certificate error, a redirect error, a wrong status code and a failed content check.
   • A slow page is marked "degraded"; that does not count as an outage.
   • Pages can be paused without losing their history.

   Automatic page discovery

   • ServerScope finds pages through robots.txt, XML sitemaps (including sitemap indexes and compressed sitemaps) and internal links.
   • Safe by default: at most 50 pages, only your own domain, and discovered pages wait for your approval. Broader settings must be confirmed explicitly.
   • Approve or reject discovered pages at once with bulk actions.

   Website overview

   • For each website you see how many pages are healthy, degraded or down, and which pages were not checked recently.
   • It also shows the average response time and p50/p95/p99 values, daily availability, active incidents and recent content, DNS and certificate changes.
   • Search, sort, filter and bulk actions in the page list.

   Content change tracking

   • ServerScope notices when the text of a page changes and shows what was added and removed.
   • Dates, times, counters and session codes are ignored by default. You can also pick one part of the page or exclude dynamic blocks.
   • A change is never an outage by itself. Acknowledge expected changes with one click, and turn on notifications per page if you want them.
   • You can also track selected response headers, so you see when a security header changes, for example.

   Smarter incidents

   • Record which website runs on which server and which services it depends on (for example server → Nginx → website → MySQL). When a server fails, you get one incident with the affected websites underneath, instead of a stream of separate alerts.
   • When several pages fail for the same reason, that becomes one website incident with details per page. A single page returning a 404 stays its own incident.
   • Every grouped incident explains why it was grouped. Outages that merely happen at the same time are never combined.
   • ServerScope suggests relations itself (for example when a domain points to a server's IP address). They are only used once you confirm them.

   Services on your servers

   • The agent can now monitor Nginx, Apache, MySQL, PostgreSQL, Redis, PHP-FPM and other systemd services. You choose which ones.
   • ServerScope clearly separates a stopped service, a monitoring agent that does not respond and a server that is really unreachable. For the last two it checks whether websites on that server still respond.

   Forecasts and anomalies

   • ServerScope compares CPU, memory, swap, load, network, disk growth, response time and error rate with the resource's own history of the past week. Only clear, large deviations are shown.
   • A capacity forecast shows when a disk or memory will fill up if the current trend continues, with a range and a confidence level.
   • Every forecast states which period was used, what the trend is and why it was raised. Nothing is forecast from too little data.
   • Predictive alerts can be switched off per server, and the sensitivity can be set per server.

   System status

   • A new page shows whether ServerScope itself is working properly: is the scheduler running, is the queue keeping up, do checks run on time and are notifications delivered.

   Improved#

   • Four severity levels: Low, Medium, High and Critical. "High" is new, for alert rules, incidents, notification preferences and webhooks.
   • Recovery confirmation: an alert rule can wait for a configurable number of good samples in a row before it reports recovery. This avoids recovery alerts during a brief dip.
   • Time to detect (MTTD): besides MTTA and MTTR you now see how quickly a problem was reported as an incident after the first failed check.
   • Recurrence: an incident shows how often the same problem occurred before.
   • Notifications per resource: switch notifications off for a server, domain, page or service. Incidents are still recorded.
   • Certificate history: every certificate seen for a domain, with issuer, validity and when it was in use.
   • Reports:
     • availability targets per server, domain and page;
     • availability per page;
     • MTTD and the total duration of incidents;
     • recurring problems;
     • an overview of how much of your environment was actually monitored;
     • an export of all incidents;
     • a printable version that you can also save as a PDF.
   • Server page: charts for swap, network traffic, disk activity and network errors.
   • Data retention: the new data, such as page checks and forecasts, can also be cleaned up after a configured period.

   Agent 0.2.0#

   • New: service monitoring via SERVERSCOPE_SERVICES, disk activity, network errors, process count and a checksum of the agent itself.
   • The agent only reads data and never runs remote commands.
   • Agent 0.1.0 keeps working. Upgrading is needed for the new server data.

   API#

   • New endpoints for pages, page checks, discovery, dependencies, services, forecasts and assigning incidents.
   • Incidents now also include the time to detect, the root incident and the reason for grouping.
   • Write requests support Idempotency-Key, so a repeated request is not executed twice.
   • Existing endpoints and fields are unchanged.

   Security#

   • Every check and every discovery run uses the same protection as the existing domain monitoring. Internal, local and cloud-metadata addresses are blocked, also after a redirect, and a DNS answer cannot be switched to an internal address afterwards.
   • Sitemaps with hidden references to files are refused.
   • New administrative actions are recorded in the audit log.

   Changed behaviour#

   • When you resolve an incident by hand, you now describe the cause and the fix in a few words.
   • An incident grouped under another incident does not send its own alert while the root incident is active. Generic webhooks still receive every incident, with a reference to the root incident.

   Good to know#

   • Incidents of different servers and websites are only grouped when you have recorded their relation under Dependencies.
   • The interface is available in Dutch only for now.
   • "No problems found" means the configured checks report nothing. It is not a guarantee that a server or website is secure.
5. 26 October 2026

   v0.3.0

   • New Discord notifications: incidents, recoveries, escalations and DNS changes are posted as clear messages in your Discord channel.
   • New Notifications when servers go offline or come back online, for monitoring alerts, website outages, SSL certificates, DNS and domain registration expiry.
   • New Set a minimum severity per webhook, for example to receive critical incidents only.
   • New Send a test message to Discord from ServerScope, with an overview of all deliveries.
   • Improved The same notification is not posted again within 15 minutes, keeping your channel calm during flapping outages.
   • Improved Discord webhook URLs are stored encrypted and are never shown in full again.
   • Improved Direct links to the documentation from the sidebar and during agent installation.
6. 26 October 2026

   v0.2.0

   • New Domain monitoring: HTTP availability, SSL certificates, DNS records and domain registration expiry.
   • New Incidents with a timeline, assignment, notes and automatic recovery.
   • New E-mail and in-app notifications with per-user preferences.
   • New Public status pages for your servers and domains.
   • New REST API with personal tokens and signed webhooks.
   • New Two-factor authentication, user invitations and an audit log.
   • New Maintenance windows for servers and domains.
   • Improved Comprehensive guides in Dutch and English.
   • Improved New navigation with direct links to log in and get started.
7. 9 October 2026

   v0.1.0

   • New First version of the dashboard with CPU, memory, load average, disk and network.
   • New Agent connection over HTTPS.
   • New Dutch and English website.