hive-c0re: its otel exporter goes to the bridge, not the swarm upstream
This commit is contained in:
parent
41a7974b9e
commit
013bbe5adc
2 changed files with 9 additions and 11 deletions
|
|
@ -373,10 +373,10 @@ async fn cmd_serve(
|
|||
// cgroup files. Feeds `disk_bytes` to the OTEL exporter. See
|
||||
// container_stats::disk_sampler_loop.
|
||||
crate::container_stats::spawn_disk_sampler();
|
||||
// Per-agent container-resource OTEL export: rides the same
|
||||
// cgroup gauges out to the configured OTLP endpoint, reusing the hive
|
||||
// `services.hyperhive.otel` config (endpoint + LoadCredential auth).
|
||||
// No-op when OTEL isn't configured.
|
||||
// Per-agent container-resource OTEL export: rides the same cgroup
|
||||
// gauges out to the hive's collector on the bridge
|
||||
// (`OTEL_EXPORTER_OTLP_ENDPOINT`), unauthenticated. The swarm-otel
|
||||
// collector alone forwards upstream. No-op when the endpoint is unset.
|
||||
crate::otel_metrics::spawn_exporter(&coord.hyperhive_flake);
|
||||
// build_logs.sqlite vacuum: c0re-side (single db). Failures kept
|
||||
// 30d, successes 24h — see `build_logs::vacuum` for the rule.
|
||||
|
|
|
|||
Loading…
Reference in a new issue