Server Events

Event Sources

Events come from three places.

1. VoxelBench Plugin (automatic)

While remote monitoring is on, the plugin detects and sends these events itself. remote-monitoring.events.enabled turns detection off, and every threshold below is a default that you can change under remote-monitoring.events (see Configuration).

Performance events (category performance):

• tps_drop (warning) — TPS below 18 for at least 10 seconds
• tps_critical (error) — TPS below 10, sent immediately
• tps_recovery (info) — TPS back to 18 or more after a drop
• gc_major (warning) — Major garbage collection pauses of 200 ms or more within 5 seconds
• memory_high (warning) — Heap use at 80 % or more of the maximum; sent again only once it has gone back below 75 %
• memory_critical (error) — Heap use at 95 % or more
• player_count_high (info) — Players online at 80 % or more of the server's slots
• player_count_full (warning) — Server full

Security events (category security):

• player_op (warning) / player_deop (info) — Operator status changed
• whitelist_change — Whitelist changed (info), or turned off (warning)
• config_reload (info) — /bench reload was run

Lifecycle events (category lifecycle):

• server_start (info) — Server started
• server_stop (warning) — Server stopping, announced by the plugin
• monitoring_paused / monitoring_resumed (info) — Remote monitoring turned off or on from the game with /bench monitor remote off or on

Benchmark events (category benchmark):

• benchmark_start, benchmark_complete (info), benchmark_stopped (warning) — A benchmark or stress limit run
• test_start, test_complete (info) — A single test (/bench test)

A restart is not an event: voxelbench.com detects it when the server's boot time changes, and counts it under Restarts on the dashboard.

2. LiteBans (built into the plugin)

When the LiteBans integration is turned on (remote-monitoring.events.litebans.enabled, off by default, applied at the next server restart), the plugin sends LiteBans sanctions with the category moderation and the source litebans: ban and tempban (warning), mute, tempmute, kick, unban and unmute (info). These events name the player and the staff member; the reason is added only if you turn on include-reason. The moderation category needs an Enterprise plan or a hosting provider account.

The plugin has no other integration that sends events, and no API for other plugins to send their own. The custom category is accepted from a server on an Enterprise plan or a hosting provider account, but the VoxelBench plugin sends none.

3. Generated by voxelbench.com

voxelbench.com adds its own events to the server's timeline, with the source alert:

• when a metric alert triggers (alert_<metric>, warning, or error for Server Offline) or resolves (alert_resolved_<metric>, info), in the category lifecycle;
• when a maintenance starts or ends (maintenance_start, maintenance_end, category lifecycle);
• when the regression alert finds that a verified server's benchmark scores dropped (benchmark_regression, category benchmark).

These events do not count against your daily limit, and do not trigger event alert rules.

Event Structure

Each event has:

Titles and descriptions come from the plugin, in English; the dashboard translates the type.

Categories

Viewing Events

Events appear in two places on the server's monitoring dashboard (see Monitoring Dashboard):

1. Chart markers — Vertical dashed lines with category icons on all monitoring charts; a benchmark run is a shaded zone. Show on charts chooses which categories are drawn.
2. Events table — Chronological table below the charts, filtered by category and source, and exportable as CSV

The dashboard shows the events of the period your plan lets you read. Scripts and agents read them with GET /api/v1/servers/{id}/events.

Retention

Events are retained for 90 days and then automatically cleaned up. Security and moderation events name players (an operator granted, a sanctioned player, a moderator), so they are kept only as long as your plan lets you view them: 7 days on Pro, 30 days on Enterprise, 7 days once your plan has lapsed. On a hosting provider account, they are kept 30 days.

Limits

The day starts at midnight UTC. Past the limit, voxelbench.com refuses the server's events until the next day. An event of a category your plan does not include is refused, and the plugin stops sending that category until the next /bench reload; the metrics and the other categories carry on. A request carries 30 events at most.