We closely monitor all aspects of your server. According to the selected SLA level, our on-call organization will take appropriate actions and notify you whenever required.

To analyze the state of the system yourself, you can access all the required tools and logs that we have available. This collection of means is outlined below.


The server status vhost is running on the server’s local interface, port 2813. It is reachable only from the server itself. You can reach the status page through an SSH port forward or SOCKS proxy.

A overview of all available status pages is available at


Use ssh <hostname> -L 2813: to forward the status vhost to your local machine.

Service Status

Each configured service is monitored through the Monit daemon. To diagnose the state of individual services, access the Monit service manager at


The monit status can also be checked in the terminal with service-summary as the devop user (see Generic Admin User).

Apache Status

The status module allows you to find out how well the server is performing. An HTML page is presented that gives the current server statistics in an easily readable form. The server-status page may be used as a starting place for troubleshooting a situation where your server is consuming all available resources, and you wish to identify which requests or clients are causing the problem.

Also, you can find all information related to Let’s Encrypt certificates (“Managed Certificates” section) and OCSP certificate stapling (“Managed Staplings” section) on the Apache status page.

You can reach the Apache status page at

PHP Status

The PHP pool status page does report configuration information about the current PHP FPM pool, and displays a list of all running processes and their state.

You can reach the PHP status page at<website-name>/.


Netdata is a real-time, interactive web dashboard that collects data every second. Metrics are saved in memory and kept for 1 hour only. You can reach its webinterface at


System statistics are collected every 10 seconds by collectd and written to RRD files in /var/lib/collectd. For performance reasons, we don’t create graphs by default. Therefore you have to download and render them yourself with a tool of your choice.


To generate performance graphs out of those RRD files, we provide a Collectd-web container, which we use ourselves to analyze workloads for our customers.


An automatic reboot is initiated to resolve from high usage scenarios due to overload:

  • 5 minute average load higher than CPU count * 10 for 5 minutes

  • memory usage higher than 95% for 5 minutes