Performance, monitoring and activity

These tabs are under Server on every server: Performance, Monitoring and Activity, and on most game servers also Player statistics. Everyone you share the server with sees the first three; player statistics, whoever may manage the game.

Performance

A data point is added every minute. At the top you choose 1 hour, 24 hours, 7 days or 30 days; dragging across a chart zooms into a section, and Reset goes back. Each curve shows low, mean, peak and, where there is one, your plan's limit. The live values are on the overview and in the console.

• Game servers: CPU, memory, storage, network and players, with starts and stops marked in the history. If the game reports its tick rate, that is shown too.
• Minecraft: with Record TPS history the portal asks for “tps” once a minute (20 is the target); the log gets one line a minute for it. It is on from the start with Paper, Purpur, Folia and Spigot. Anyone allowed to use the console can switch it.
• VPS and containers: measured by our system outside the server, nothing of it runs on your server. CPU, memory, network, disk access, storage used and how much of the time the server was running.
• Under Traffic, a VPS or container shows how much the server sent and received in the current billing term, per day and for earlier terms, and how much is included if your plan names an amount.

Monitoring

Under Monitoring, from our network in Germany we check at your interval whether your service answers from outside, and let you know if it does not. This tells you it is reachable, not that it runs without errors. The owner and anyone with the Setup right can set it up.

• A game server has exactly one check, Game answers: we ask the game in its own format, for Minecraft like the in-game server list, for Steam games like the server browser. If a game has no query, we only check that the server runs; the page says so.
• A VPS or container has up to 10 checks (50 in the whole account): Website (status code, keyword, certificate expiry), TCP port, UDP port, Ping, DNS or a Database (MySQL/MariaDB, PostgreSQL, Redis, MongoDB, without signing in). Only addresses of this server, or names pointing to them, are checked. Invert alerts when a target answers, such as a port that should stay closed.
• You choose how often (every minute, every 5 or every 15 minutes) and after how many failures in a row we let you know, so that a short network glitch sends no alert.
• Each check shows how reachable it was in the last 24 hours, its response time and its outages over 24 hours, 7 or 30 days. Each check has Check now, Pause and removing it (by holding).

Alerts go through the channels you chose under Notifications, once per outage and as a reminder at most every six hours. Your network checks also count towards a credit for outages.

Alerts on load

Under Load you switch on alerts from the readings we take every minute anyway; you set the limit and the duration yourself. For game servers: Memory, CPU and, if the game reports it, the Tick rate. For a VPS or container also Off without being stopped, Storage almost full (on from the start, at 90 %; a VM only reports this with the guest agent installed) and High traffic (once per term).

All checks at a glance

In the server list, Monitoring leads to every check on every server in your account: whatever gets no answer right now is at the top, below it the servers without a check yet. Each row leads to its server's tab.

Activity

• Who did what to the server and when, including our support and automatic things such as schedules. Stored with us, not on the server.
• Filter by Area, Who and Period, or search by action, name or file. Export downloads the entries shown as CSV, Load older fetches earlier ones.
• The address an action came from is visible to the owner on every entry, and to everyone else only on their own.
• On game servers, Shared logs below lists the logs you shared from the console, with the date they are deleted. Delete now ends a link at once.

Player statistics

Player statistics shows who plays when, over 7 or 30 days. For Minecraft the portal reads the server's log, the first time up to 90 days back: players per day, new and returning, playtime, sessions, when it is busiest and every player with their first and last visit. For other games, or when the log cannot be read or is larger than 32 MB, it comes from the player count we ask for every minute: peaks and busy hours, but no names.