glue-controller-env: the controller always exports otlp to the swarm's collector
This commit is contained in:
parent
ed76419be7
commit
2507f4f713
3 changed files with 45 additions and 17 deletions
|
|
@ -198,6 +198,10 @@ and failure series on `collector` appear once something fails.
|
|||
|
||||
**Where the data comes from.** The swarm's OTEL collector, below.
|
||||
|
||||
The `controller` panels come from the controller itself. It exports OTLP
|
||||
through the gateway to the swarm's collector from whatever host it runs on,
|
||||
whether or not that host runs the collector.
|
||||
|
||||
Neither container is reachable except through the gateway: each listens
|
||||
on a unix socket only the gateway's nginx can open, and VictoriaMetrics
|
||||
runs in a network namespace of its own with no interface but loopback.
|
||||
|
|
|
|||
Loading…
Reference in a new issue