{"version":"2.1.288","anchor":"runner-health-server-restricts-v1metrics-by-a-shared-check","canonical_anchor":"runner-health-server-restricts-v1metrics-by-a-shared-check","heading":"Self-hosted runner changes who may read its metrics page","tier":"internal","area":"Elsewhere","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/runner-health-server-restricts-v1metrics-by-a-shared-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Self-hosted runner changes who may read its metrics page\n\nThe self-hosted runner's health server now decides who may read `\/v1\/metrics` with a shared check instead of a fixed list of local addresses\n\n**Unclear.** It is not clear which callers the new check allows.\n\n**What**\n\nA self-hosted runner, a machine you run yourself to execute Claude Code jobs, has a small built-in health server. That server now uses a shared check to decide who may read `\/v1\/metrics`. Before, only requests from the machine itself were allowed, based on a fixed list of local addresses.\n\n**Why**\n\nThe rule for who can read the runner's metrics has changed. If you collect metrics from a runner, check that your collector can still reach this page.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}