| Filename | Latest commit message | Latest commit date |
|---|---|---|
76f6b7c3b7
hive-c0re's container-resource exporter has POSTed to a 404 for as long as it has existed, silently: it passed the collector's base address to `with_endpoint`, which the SDK takes verbatim, so every export went to `/` instead of `/v1/metrics`. Nothing reported it — OTLP export failures go to an error handler no binary here installs — so the daemon logged "exporter enabled" and delivered nothing. VictoriaMetrics has never held a sample under `service.name=hyperhive-c0re`. Fix the way the rest of the repo already resolves an endpoint: an endpoint option names a BASE, and the layer that knows the signal appends to it. `hive-metric` — same SDK, same collector — never calls `with_endpoint`, and `docs/observability.md` documents the append as system behaviour; the one place a full path is spelled out is the VictoriaMetrics exporter, because its far end is not a standard OTLP path. So drop the call. The builder is now byte-identical to hive-metric's, and hive-c0re's unit carries the standard `OTEL_EXPORTER_OTLP_ENDPOINT` for the SDK to read. The address is bound once in nix and consumed twice, so what a hive hands its agents and what it exports to itself cannot drift. The enable signal moves to that same standard variable: "configured" and "where it actually goes" become one string rather than two that agree by convention. `HYPERHIVE_OTEL_*` keeps its own job, the agent-config transport meta.rs reads — a name the SDK has never known, which is the bug. The test changes shape with the fix. The old one asserted a URL this module built; the new one pins that the exporter is gated on the variable the SDK itself reads, because the fix is now an absence and an absence is what a later "the endpoint is right there, just pass it" edit puts back. Refs #3402 |
||
| .. | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
hive-c0re
The unprivileged host daemon (runs as hive-core). Owns the sqlite
broker, the approval/question/schedule queues, the generic job-DAG
queue, container lifecycle, gateway/forge/matrix provisioning,
per-container stats, and the axum operator dashboard. Largest crate in
the workspace — bin-only, no separate lib.
When to use it
Host-level, cross-container orchestration: spawning/rebuilding/
destroying agent containers, the approval flow, dashboard-visible
state, provisioning per-agent forge/matrix/gateway accounts. Agent-side
behavior (turn loop, MCP tools) lives in hive-agent/hive-agent-mcp
instead — this daemon only talks to agents over the socket wire types
in hive-sh4re.
Shape
Cohesive clusters live in directory submodules, each re-exported at
the crate root (crate::broker::… keeps resolving regardless of which
subdirectory a module actually lives in). One line each — read the
module's own //! doc-comment for real detail, don't expect this file
to track it:
dashboard/— the operator dashboard (containers, approvals, schedules, questions, logs, topology).job_queue/— the job-DAG queue + desired-state reconciliation (docs/coordinator.md).lifecycle/—nixos-containerlifecycle + per-agent config flake generation.stores/— sqlite-backed stores (broker, queues, audit, power).workers/— background sweeps (crash watch, scheduled prompts, auto-update, knowledge sync).agent_config/— per-agent registries (tool groups, capabilities, resource limits, topology).stats/— dashboard metrics aggregation + OTEL export.socket_server/— the unix-socket request server shared by per-agent + manager sockets.forge/— optional Forgejo wiring (docs/forge.md).coordinator.rs— top-level wiring forserve.meta.rs,migrate.rs— the meta flake + schema/state migrations.matrix.rs,gateway_nginx.rs,webhook_secret.rs,priv_client.rs— matrix provisioning, gateway vhosts, webhook secrets, and thehive-privclient respectively.
See the top-level CLAUDE.md/docs/ index for the full reading-path
map.