vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Activity

docs: state current behaviour without change-log wording

Browse source
This commit is contained in:
atlas 2026-10-02 09:44:06 +02:00
commit 195cf75bbf
4 changed files with 14 additions and 18 deletions
Download patch file Download diff file Expand all files Collapse all files

9
docs/scheduler/observability.md
View file

@ -58,7 +58,7 @@ the control plane, so degraded telemetry isn't degraded operation.
### Why two tiers
**The hive tier isn't optional.** Exporting straight to `endpoint` would mean
**Agents export only to the hive tier.** Exporting straight to `endpoint` would mean
every agent needs the credential — and the only place to hand it to an agent
container is somewhere the agent itself can read, its own claude settings
among them. `0600` protects a secret from other containers, not from the
@ -98,10 +98,9 @@ hive's collector can label its data as any other agent.
**Logs ride the same hop, and a journal carries more than a counter does.** Each
agent container forwards its own journal through this port — every unit in it at
`info` and above, not an allowlist. That's the harness, the MCP daemons and
whatever a tool call spawned, so command lines and error text now leave the
container, not just counts. The trust boundary is unchanged (same
destination, same credential, and an agent could already send arbitrary OTLP);
what changes is how much detail leaves by default.
whatever a tool call spawned, so command lines and error text leave the
container, not just counts. Destination, credential and trust boundary are the
same as for any OTLP the agent sends.
<!-- vale write-good.Passive = YES -->