Content generated with AI — it may contain mistakes.

ExyliaAnalytics/GuidesUpdated in v1.2.0

Monitor servers and performance

The Servers page — status, rename, pause, revoke and the proxy mapping — and the Health tab with TPS, server lag, CPU, memory, uptime, restarts and crashes.

Page 7 of 287 min read

In a few minutes you can tell which of your servers are reporting, stop one from collecting, retire one for good, tell the dashboard which game server is which entry of your proxy, and see whether the hardware keeps up with your players.

Before you start#

You need at least one server linked to the workspace, see Connect your server. Rename, pause, resume, revoke and the proxy mapping need the Connect, rename, disable and revoke servers permission; everyone else can read the pages.

Steps#

Open the Servers page

In the sidebar, under Workspace, open Servers. The Status tab lists every server linked to the workspace. The other tabs are Health and Connect a server.

Read the status

Check the Status column. Online means its signals are arriving. See the table under Status for the rest.

Rename it

Use Rename on a row and give the server a name you will recognise, up to 40 characters.

Pause or revoke when needed

Pause stops one server from collecting for a while, and Revoke retires it for good. Both are explained below.

Match game servers to your proxy

If you run a proxy, confirm each game server once in Proxy mapping, see Proxy mapping.

Check the Health tab

Open Health to see uptime, restarts, crashes, server speed and lag per server, then pick one server in the filter bar for the charts.

Check that it works#

The server shows Online, the Online column counts the players on it, and Last signal says a minute or less ago. On Health, its row shows an uptime, and the charts fill after the first metrics interval (60 seconds by default).

Going further#

The server table#

ColumnShows
NameEditable by members who manage servers, up to 40 characters.
TypeProxy, game server or standalone, as the agent reported on its last start.
SoftwarePlatform and Minecraft version, and the agent version. An Update available badge appears when a newer agent exists.
StatusSee below.
Last signalHow long ago the server last reported in.
OnlinePlayers on it right now, while it is online.
PluginThe agent version it runs.

Status#

StatusMeaning
WaitingLinked, but no signal has arrived yet.
OnlineIts signals are arriving.
SilentIt missed three signals in a row (three minutes with the default interval). Its open sessions and stays are closed at the last signal, as Timed out.
DisabledPaused from this page.
RevokedIts key no longer works.

A server that stops cleanly sends a stop before going quiet, so the dashboard can tell a restart from a crash: a start whose previous run never sent that stop is marked as a crash on every chart.

Pause and resume#

Pause is a kill switch for one server. The agent learns it with its next batch, stops collecting and stops sending; /analytics status shows "Disabled from the dashboard". Nothing it sees while paused is ever sent.

Resuming needs the server to ask again

A paused agent sends nothing, so it never hears that it was resumed. After Resume, run /analytics reload on that server (/analyticsv reload on the proxy) or restart it. Its first start after a pause is marked on the charts as a crash, since the paused run never sent a stop.

Revoke#

Revoke retires a server for good. Its key stops working within 30 seconds; the agent is told on its next send, logs "This server's token was revoked", deletes its credentials and whatever it had not sent, and goes back to unlinked. What it had already sent stays in the workspace. To bring it back, link it again with a new connection code: it becomes a new server.

Proxy mapping#

A proxy reports its own server list, each entry's name and address, when it starts and whenever the list changes. A game server does not know what the proxy calls it, so the dashboard asks you to match them once:

  • The Proxy mapping table lists every game server with its Port and the Proxy entry it belongs to, and suggests the entry with the same port, marked Suggested.
  • Nothing is saved until you Confirm (or Save after picking another entry). The match is stored and never guessed again.
  • An entry with no confirmed game server is shown as Not matched: confirm a match, or install the agent on that server.

The table only appears once the workspace has both a proxy that reported its list and at least one game server.

Season#

Season on a server sets its Season start. The in-game economy only counts money from that day on, so a season reset does not read as a collapse.

Health#

Is the hardware keeping up with the players? The Health tab has one row per server, then charts for the server picked in the filter bar.

Health table columns
ColumnDefinition
StatusAs on the Status tab.
UptimeShare of the range covered by signals.
RestartsStarts reported in the range.
CrashesStarts not preceded by a stop.
Server speed (TPS)Average ticks per second.
Server lag, slowest 5%The slowest 5% of ticks (MSPT p95), in milliseconds.
Minutes of lagMinutes with players online where the server averaged under 18 TPS, froze under 10 TPS for a second, or its slowest 5% of ticks took over 50 ms. A lone split-second hiccup does not count.
CPUShare of all cores the server's process used.
Peak memoryThe most Java heap in use.
Most players onlineThe most players online at once.

A Server health now table sums it up: OK means the server meets the speed and tick-time thresholds, and Down means no signal for three intervals. Proxies have no TPS or lag figures.

Health charts
ChartShows
Server lagAverage and slowest-5% tick time, with the 50 ms line above which a server falls behind 20 TPS.
Server speedAverage and lowest TPS.
LagMinutes per period of lag.
UptimeShare of each period covered by signals, with restarts and crashes.
CPUThis server's process against the whole machine.
MemoryJava heap in use against the maximum.
Players on this serverAverage and peak online.
Entities and chunksWhat the world asks of each tick.
Restarts and crashesEvery start in the range, labelled restart, crash or agent update.
Lag eventsRuns of lag minutes in a row.
Does lag drive new players away?New players against lag, so you can see whether the two move together.

What each platform can report#

MeasurePaperSpigotFoliaVelocity
TPS✓✓Global region only—
MSPT✓—Global region only—
CPU and heap✓✓✓✓
Entities and chunks✓✓——
Players✓✓✓✓

TPS is measured by the agent itself, from how long 20 ticks really take. MSPT comes from Paper's tick-end event, which Spigot does not have. On Folia the agent runs on the global region, which keeps its own pace whatever the world regions do, so its TPS and MSPT read as idle and entity and chunk counts are not reported at all.

Samples are taken every second and summarised into one row every metrics interval (60 seconds by default, set in Remote configuration). Raw metrics are kept for 90 days; older ranges read hourly and daily summaries.

Something missing on this page? Tell us on Discord