{"version":"2.1.318","anchor":"remote-runner-exposes-session-turn-state-metric","canonical_anchor":"remote-runner-exposes-session-turn-state-metric","heading":"Remote runners report whether each session is busy, waiting, resting or lost","tier":"use","area":"Self-Hosted Runner","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/remote-runner-exposes-session-turn-state-metric","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Remote runners report whether each session is busy, waiting, resting or lost\n\nRemote runners now publish a session_turn_state metric that shows each session as busy, waiting, rest or lost\n\n**What**\n\nWhen Claude Code runs on a remote runner (a machine that hosts Claude Code sessions for other people or systems), it publishes metrics in Prometheus format. Prometheus is a common monitoring tool that collects numbers from running programs. These metrics now include a new gauge, `session_turn_state`. A gauge is a value that can go up and down over time. The gauge reports which state a session's turn is in:\n\n- `busy`\n\n- `waiting`\n\n- `rest`\n\n- `lost`\n\n**Why**\n\nIf you run a pool of runners, you can now see from your monitoring which sessions are working, which are waiting, which are idle and which have been lost.\n\n- Area: Self-Hosted Runner\n- Names: `session_turn_state`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}