fix(hive-metric): blocking OTLP client (no-reactor panic), reject negative counters, allow negative gauges

hive-metric/src/main.rs

@@ -24,13 +24,19 @@ use opentelemetry_otlp::{Protocol, WithExportConfig};
 #[derive(Parser)]
 #[command(
     name = "hive-metric",
-    about = "Push a labeled metric to the OTEL collector (requires services.hyperhive.otel.enable = true)"
+    about = "Push a labeled metric to the OTEL collector (requires services.hyperhive.otel.enable = true)",
+    // Let a leading-minus value parse as the `value` positional rather than
+    // being rejected as an unknown flag — negative gauges are legitimate
+    // (e.g. a delta), and it lets the counter-sign check below produce a clear
+    // domain error instead of clap's "unexpected argument '-1'".
+    allow_negative_numbers = true
 )]
 struct Cli {
     /// Metric name (e.g. `tasks_completed`, `latency_ms`).
     name: String,
 
-    /// Numeric value (f64). Floats and integers both accepted.
+    /// Numeric value (f64). Floats and integers both accepted. Gauges may be
+    /// negative; counters must be >= 0 (they only increase).
     value: f64,
 
     /// Metric kind: `counter` (cumulative sum, default) or `gauge` (instantaneous value).
@@ -52,8 +58,7 @@ enum MetricKind {
     Gauge,
 }
 
-#[tokio::main]
-async fn main() -> Result<()> {
+fn main() -> Result<()> {
     let cli = Cli::parse();
 
     // Fail early with a clear message when OTEL is not configured.
@@ -66,6 +71,18 @@ async fn main() -> Result<()> {
 
     let labels = parse_labels(&cli.labels)?;
 
+    // Counters are monotonically non-negative — the OTEL SDK silently drops a
+    // negative `add`, so a typo like `hive-metric tasks_done -1` would vanish
+    // with exit 0. Reject it loudly instead.
+    if matches!(cli.metric_type, MetricKind::Counter) && cli.value < 0.0 {
+        bail!(
+            "counter '{}' value must be >= 0 (got {}); counters only increase — \
+             use `--type gauge` for a value that can go down",
+            cli.name,
+            cli.value
+        );
+    }
+
     let exporter = opentelemetry_otlp::MetricExporter::builder()
         .with_http()
         .with_protocol(Protocol::HttpJson)
@@ -73,6 +90,12 @@ async fn main() -> Result<()> {
         .context("failed to build OTLP metric exporter")?;
 
     // SDK automatically reads OTEL_RESOURCE_ATTRIBUTES for resource labels.
+    // The metrics SDK has no `with_simple_exporter` (that's a *traces*-only
+    // API) — a push exporter is always driven by a periodic reader. For this
+    // fire-and-forget CLI the timer never actually fires: we record one metric
+    // and immediately `shutdown()`, which force-flushes the pending export
+    // synchronously before returning. So there's no background-timer flush race
+    // in practice — the single point is exported exactly once on shutdown.
     let provider = opentelemetry_sdk::metrics::SdkMeterProvider::builder()
         .with_periodic_exporter(exporter)
         .build();