Watch
0
0
Fork
You've already forked hyperhive
0

ship the cache's init units' journal from a host with no collector, with the cache's own client

This commit is contained in:
maia 2026-11-18 03:38:07 +01:00 • committed by mara
commit a3682a5e9a
2 changed files with 137 additions and 7 deletions

View file

@ -396,6 +396,8 @@ A host that runs the cache without the swarm collector adds `swarm-bao-attic-sec
and `swarm-bao-attic-tokens.service`; a host that runs the archive adds `swarm-archive.service`, `swarm-archive-users.service`, `swarm-archive-prune.service` and `swarm-archive-check.service`, and a hive adds `hive-archive-backup.service`.
A host that also runs the swarm collector names none of these: its whole-host journal receiver
ships them already, and the hive collector then has no `journald` receiver.
A host that runs the cache and neither collector ships the cache's two units with
its own journal forwarder instead (see [the cache's journal](../swarm/builder.md)).
No bind mount is needed. Unlike an agent's journal, this collector already
shares a filesystem with the units it reads, because it's a host systemd
service rather than a container. It forwards the crash log line alongside the

View file

@ -751,5 +751,10 @@ The container forwards atticd's journal to the swarm collector like the other
service containers (see [Telemetry collector](telemetry.md#telemetry-collector-otel)). The two host
units' lines reach the log store too: through the hive collector's journal
allow-list on a hive host, or through the swarm collector's whole-journal
receiver where the host runs that. A host with neither keeps them in its own
journal.
receiver where the host runs that. A host with neither runs the container's
forwarder module on the host itself, for those two units only. It logs in with
the `attic` leaf, reads the cache's own OIDC client secret and pushes to the
cache's route on the swarm collector, so it needs no new client, grant or leaf.
The records carry `service.name` `attic-host`. It only ships the cache's two
units: another swarm service's host units on such a host stay in its own
journal, because each service has its own client.