swarm-otel: route the gateway from the receiver list and check the sockets accept
Refs #4815
This commit is contained in:
parent
ec562ca503
commit
1325f44707
3 changed files with 123 additions and 19 deletions
|
|
@ -334,7 +334,11 @@ It runs in a `swarm-otel` container on the hive bridge, in a network
|
|||
namespace of its own. It binds no OTLP port: every receiver (one per hive,
|
||||
the swarm tier's and one per service forwarder) listens on a unix socket in
|
||||
`/run/swarm-otel`, a directory only the gateway's nginx and the container can
|
||||
open, and the gateway forwards to them.
|
||||
open, and the gateway forwards to them. The gateway's routes and the collector's
|
||||
receivers come from one list, so they name the same sockets. The
|
||||
`swarm-otel-sockets` unit connects to each socket as the gateway's user after
|
||||
the container starts and fails if one refuses for 30 seconds, so a collector
|
||||
that's up but not listening shows as a failed unit.
|
||||
|
||||
Every hive's own collector reaches this one by its gateway name,
|
||||
`swarm.otel.domain` (default `otel.<swarm domain>`) — the same
|
||||
|
|
|
|||
Loading…
Reference in a new issue