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

hive-c0re: the OTEL exporter doc says it is what the container stats feed, not a second consumer

Browse source
This commit is contained in:
iris 2026-10-15 00:17:00 +02:00 • committed by mara
commit 1a86304f92
1 changed files with 3 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

7
hive-c0re/src/stats/otel_metrics.rs
View file

@ -1,6 +1,5 @@
//! Per-agent container-resource OTEL export. hive-c0re already samples each
//! agent container's cgroup load for the dashboard
//! ([`super::container_stats`]); this rides those same gauges out to the
//! Per-agent container-resource OTEL export. This is what the cgroup load
//! sampled in [`super::container_stats`] feeds: it rides those gauges out to the
//! 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 from the same binding it hands agents). No toggle of
@ -194,7 +193,7 @@ fn register_instruments(provider: &SdkMeterProvider, snapshot: Arc<Mutex<Vec<Con
.build();
// Custom (`hyperhive.`) metrics semconv doesn't standardise: memory peak,
// on-disk footprint, and the instantaneous cpu percent the dashboard shows.
// on-disk footprint, and the instantaneous cpu percent.
let snap = snapshot.clone();
meter
.u64_observable_gauge("hyperhive.container.memory.peak")