Metrics, events & telemetry

Collected metrics

Metrics are numeric time series you can chart (and alert on in the future), for example:

• Online player count
• Cpu / memory usage
• Disk usage and size
• Tick rate
• Millis per tick with different statistics (median, min, max, p95)
• Players latency (avg, min, max, p95)

Collected events

Events represent discrete occurrences, for example:

• Player joined / left
• Player deaths
• Player commands executed
• Player teleports, which includes dimension changes
• World statistics snapshots (e.g. number of loaded chunks, entities, tile entities, etc) -> might be moved to metrics in the future for better compression
• Server start -> Server Load -> Server Stop
• Plugin enable/disable

Addon events (if you have addons installed) may also be collected, for example:

• LuckPerms
  • User group changes
• DeluxeMenus
  • Menu opens
  • Button clicks
  • Menu closes
• WorldGuard
  • Region enters/exits, including the duration spent in the region
• Votifier
  • Vote received, if the player is on the server at the time

Player telemetry

Telemetry is player-scoped behavioral data used to build funnels, cohorts, and session views.

We collect periodically:

• Player position (x, y, z, dimension)
• Latency

With this and player join/leave events, we derive:

• Session start/end
• Playtime duration
• Travel map (based on position updates)

Notes on privacy and identifiers

• Prefer pseudonymous identifiers where possible.
• Avoid sending sensitive personal data in event properties.