hive-c0re/Cargo.toml

@@ -20,15 +20,12 @@ clap.workspace = true
 clap_complete.workspace = true
 clap-markdown = "0.1"
 # OTEL SDK for the per-agent container-resource metrics exporter
-# (stats/otel_metrics.rs). Same versions as hive-metric — the blocking OTLP
+# (stats/otel_metrics.rs). Same versions/features as hive-metric — the
-# client is deliberate: the metrics SDK's PeriodicReader runs on a background
+# blocking OTLP client is deliberate: the metrics SDK's PeriodicReader runs
-# thread with no Tokio reactor, where the async client panics.
+# on a background thread with no Tokio reactor, where the async client panics.
 opentelemetry = "0.32"
 opentelemetry_sdk = { version = "0.32", features = ["metrics"] }
 opentelemetry-otlp = { version = "0.32", default-features = false, features = [
-  # Not a transport: it is in `default`, so `default-features = false` drops the
-  # exporter's own diagnostics unless it is named here.
-  "internal-logs",
   "metrics",
   "http-json",
   "reqwest-blocking-client",

hive-metric/Cargo.toml

@@ -19,8 +19,6 @@ opentelemetry_sdk = { version = "0.32", features = ["metrics"] }
 # so the async client panics there with "no reactor running". The blocking
 # client sends on that thread directly — and for a fire-and-forget CLI that
 # records one point then `shutdown()`s, a synchronous send is exactly right.
-# No `internal-logs` here, unlike hive-c0re: this binary installs no tracing
-# subscriber, so the SDK's diagnostics would have nowhere to go.
 opentelemetry-otlp = { version = "0.32", default-features = false, features = [
   "metrics",
   "http-json",