Server Events

Event Sources

Events can come from three places:

1. VoxelBench Plugin (automatic)

The plugin automatically detects and sends events:

Performance events:

• tps_drop — TPS sustained below threshold for 10s
• tps_critical — TPS dropped critically low (immediate)
• tps_recovery — TPS recovered to normal
• gc_major — GC pause exceeding 200ms

Memory events:

• memory_high — RAM usage above 80% (with 5% hysteresis)
• memory_critical — RAM usage above 95%

Security events:

• player_op / player_deop — Operator status changed
• whitelist_change — Whitelist modified
• config_reload — Server configuration reloaded

Player events:

• player_count_high — Player count above 80% of max slots
• player_count_full — Server full

Lifecycle events:

• server_start — Server started
• server_stop — Server stopped
• restart — Server restarted (boot timestamp changed)

2. Third-Party Plugins (via VoxelBench API)

Other plugins can send events through the VoxelBench plugin API:

• LiteBans: ban, tempban, mute, tempmute, kick, unban, unmute
• Anticheat plugins: flag, punish, alert
• Any plugin can register custom events

3. Backend-Generated (from metric alerts)

When a metric alert triggers or resolves, the backend automatically creates an event. This bridges the two systems so all alert activity appears in the events timeline.

Event Structure

Each event has:

Categories

Viewing Events

Events appear in two places on the dashboard:

1. Chart markers — Vertical dashed lines with category icons on all monitoring charts
2. Events table — Chronological table below the charts with filtering by category and source

Retention

Events are retained for 90 days and then automatically cleaned up.