From 016caaa3d26f13511894268ee9f017c0940e42c7 Mon Sep 17 00:00:00 2001 From: iris Date: Tue, 10 Nov 2026 19:12:01 +0100 Subject: [PATCH] docs: the services page describes the ci runner board and its runner filter The board gained a Runner filter and one series per runner; the CI runner section now says what the board shows and how it differs from the forge's CI runs tab. --- docs/2-handbook/swarm/services.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/2-handbook/swarm/services.md b/docs/2-handbook/swarm/services.md index 328b2cc49..2c6e48c4d 100644 --- a/docs/2-handbook/swarm/services.md +++ b/docs/2-handbook/swarm/services.md @@ -502,6 +502,13 @@ nothing listens on the bridge. Series, all prefixed `gitea_runner_`: namespace and can read the endpoint, which carries counts, durations, the runner's name and its version, and no secrets. +The **ci runner** board in Grafana shows these series. Its **Runner** filter +(the series' `service.instance.id`, the scrape address) narrows every panel, +and uptime, job slots and slot use show one series per runner, so a runner +registered by hand appears beside the swarm's once its metrics reach the +store under its own instance id. The forge's **CI runs** tab is the other +view: run times and queue wait of every run, whichever runner ran it. + ### Builder The swarm builder, in a `swarm-builder` container on the host that sets