every hive runs its otel collector, and agents export to it by default
This commit is contained in:
parent
839efd1642
commit
13daf4c7dc
28 changed files with 245 additions and 303 deletions
|
|
@ -117,8 +117,8 @@ dnsmasq is **authoritative** for the hive's own zone (`<hive-domain>`)
|
|||
plus whatever swarm-service names this host contributes via
|
||||
`gateway.localNames` — `forge.<swarm-domain>` and `chat.<swarm-domain>`
|
||||
(matrix) when this host runs those services, `auth.<swarm-domain>`
|
||||
when it runs authelia, and `hive-collector.<swarm-domain>` on every hive
|
||||
with `otel.enable` — answering each with the bridge IP (where nginx
|
||||
when it runs authelia, and `hive-collector.hive` on every hive
|
||||
— answering each with the bridge IP (where nginx
|
||||
is reachable, and where the hive's own collector listens). Note forge and
|
||||
matrix are swarm-domain names, not sub-domains of `<hive-domain>`: a swarm
|
||||
runs one forge and one homeserver, so their names belong to the swarm rather
|
||||
|
|
@ -182,7 +182,7 @@ By default agents can only reach the host on 80/443 (+53 DNS), so a
|
|||
host-side service on another port — for example a dev OTLP collector you want
|
||||
agents to reach directly — is unreachable. (hyperhive's own services
|
||||
need none of this: a module that means to be reachable from agents opens
|
||||
its own port here, which `otel.enable` and `nats.enable` both do. Note
|
||||
its own port here, which the hive collector and `nats.enable` both do. Note
|
||||
that `otel.endpoint` is the _upstream_, which no agent ever dials. See
|
||||
`docs/scheduler/observability.md`.)
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue