Get server resource metrics
Returns CPU, memory, network, load, and connection metrics for a running server over a configurable time window. Each metric is a time series of {t, v} data points where t is a Unix timestamp and v is the metric value.
Use period to control the time window (e.g., 1h for last hour) and step for data point resolution (e.g., 60s for one point per minute).
Only available for servers that are currently running.
Authorizations
Path Parameters
Server instance ID.
Query Parameters
Relative time window for metrics (used when start_time is omitted). "5m": last 5 minutes, "15m": last 15 minutes, "1h": last hour, "6h": last 6 hours, "24h": last 24 hours.
5m, 15m, 1h, 6h, 24h Data point interval. Smaller steps give higher resolution but more data. "15s": every 15 seconds … "1800s": every 30 minutes. Scale it to the window (a wide window needs a coarse step).
15s, 30s, 60s, 300s, 600s, 1800s Absolute window start — ISO 8601 (e.g., "2026-07-12T03:00:00Z") or relative (e.g., "-6h"). When set it OVERRIDES period, so you can inspect a specific interval (pair with end_time).
Absolute window end — ISO 8601. Defaults to now. Use with start_time for a fixed interval (e.g., a past incident window).
Response
Server resource metrics over the requested time window.
Server resource metrics including CPU, memory, network, load, and connections over a configurable time window.
Server instance ID.
Fly.io machine ID providing these metrics.
Fly.io region code (e.g., "ewr", "fra").
PlayFlow compute size of the machine (e.g. "small", "large").
Number of vCPUs allocated to the machine, derived from compute_size. Threshold the 1-minute load average against this: at/above vcpus is a warning, at/above 2× is an overload likely to freeze the game loop. Null when the size is unknown.
Restart/stop/OOM markers for the charts.
Time window and resolution for the returned metrics.
CPU usage metrics, broken down to surface I/O-wait and steal which are typical freeze culprits.
Memory usage metrics.
Network I/O metrics (bytes, packets, and — for freeze diagnosis — dropped/error rates).
System load average metrics over 1/5/15-minute windows.
Network connection metrics.