feat(#3125): a swarm-tier OTEL collector, in its own container
The swarm tier is the only holder of the upstream credential, the only writer to the swarm's metrics store, and (once #3283 lands) the place that stamps hive= from the authenticated connection rather than from anything a sender can choose. Today one collector does both tiers' jobs, which works only because they land on one box. A container rather than a second host unit, for two reasons that agree: every sibling swarm service is one, and `services.opentelemetry-collector` is a singleton NixOS option already spoken for on the host by the hive tier. A container gets its own evaluation and therefore its own collector. Port defaults to 4319, deliberately not the OTLP default 4318 the hive tier uses: swarm containers share the host netns, and two listeners claiming one port is not a build failure but a runtime coin toss with nothing in any log saying so -- the same collision grafana and the forge hit on 3000. `url` is an option with a co-located default rather than a loopback literal in the exporter, so a split-host deployment is a config change instead of a code change. Wires nothing yet: the hive tier still exports directly, and switching it over is the next commit.
This commit is contained in:
parent
5fdbf0b452
commit
f61c927310
2 changed files with 214 additions and 0 deletions
|
|
@ -27,6 +27,7 @@
|
|||
./swarm-nats.nix
|
||||
./swarm-controller.nix
|
||||
./swarm-grafana.nix
|
||||
./swarm-otel.nix
|
||||
./swarm-snapshot-store.nix
|
||||
./swarm-ui.nix
|
||||
./swarm-victoriametrics.nix
|
||||
|
|
|
|||
Loading…
Reference in a new issue