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

container collectors scrape their own telemetry and push it up their hop

Browse source
This commit is contained in:
atlas 2026-10-28 22:01:33 +01:00 • committed by mara
commit 73c966a7eb
1 changed files with 163 additions and 49 deletions
Download patch file Download diff file Expand all files Collapse all files

10
docs/swarm/services.md
View file

@ -219,10 +219,12 @@ and failure series on `collector` appear once something fails, and the
collector and of the swarm's collector, which both carry the collector
binary's default `service.name`, `otelcol-contrib`. The timeseries panels
split by `server.port`: 8888 is the hive collector, 8889 the swarm
collector. The per-container collectors (the secret store, NATS, Grafana,
Authelia, the Victoria stores and the agents' forwarders) don't report
their own metrics yet, so they have no lines here; a separate issue on
the forge covers that. `scripts/check-dashboard-service-names.sh` runs in CI
collector. Every per-container collector (the secret store, the other service
containers and the agents' forwarders) also scrapes its own endpoint on
loopback and pushes the result up its normal hop, so each has a line of its
own, on its own port: agents all report on 8904, service containers on
8890 to 8903. The series carry `container` (services) or `agent` (agents)
to tell them apart. `scripts/check-dashboard-service-names.sh` runs in CI
and in `scripts/pre-push`. It fails when a dashboard query selects a
`service.name` that nothing emits.