mara/hyperhive
mara/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Activity

docs: the services page describes the ci runner board and its runner filter

Browse source 
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.
This commit is contained in:
iris 2026-11-10 19:12:01 +01:00
commit 016caaa3d2
1 changed files with 7 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/2-handbook/swarm/services.md
View file

@ -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 namespace and can read the endpoint, which carries counts, durations, the
runner's name and its version, and no secrets. 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 ### Builder
The swarm builder, in a `swarm-builder` container on the host that sets The swarm builder, in a `swarm-builder` container on the host that sets