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
|
|
@ -3,7 +3,7 @@
|
|||
//! hive's own collector — the same first hop the agents use, named by the
|
||||
//! standard `OTEL_EXPORTER_OTLP_ENDPOINT` (see `nix/host-modules/hive-c0re`,
|
||||
//! which sets it to the collector's bridge address where agents get its
|
||||
//! swarm-wide name). No toggle of
|
||||
//! fixed name). No toggle of
|
||||
//! its own, and no credential: a hive's collector takes unauthenticated OTLP
|
||||
//! on the bridge, and the only hop that presents anything is the swarm tier's,
|
||||
//! which is the one that leaves the swarm.
|
||||
|
|
@ -100,8 +100,7 @@ fn build_provider(
|
|||
hyperhive_flake: &str,
|
||||
) -> Result<SdkMeterProvider> {
|
||||
// http/json — the only OTLP transport this crate enables (matching
|
||||
// hive-metric). The Claude SDK path honours `HYPERHIVE_OTEL_PROTOCOL` for
|
||||
// its own export; this exporter is always http/json.
|
||||
// hive-metric); this exporter is always http/json.
|
||||
//
|
||||
// The address is deliberately NOT passed here. The SDK reads
|
||||
// `OTEL_EXPORTER_OTLP_ENDPOINT` itself and appends the signal path
|
||||
|
|
|
|||
Loading…
Reference in a new issue