| Filename | Latest commit message | Latest commit date |
|---|---|---|
34fed47400
mara: comments to code ratio too high. It was 16 comment lines for one line of feature. Kept only the fact that stops the feature being trimmed away again - it is not a transport, it is in `default`, so `default-features = false` drops it - and, in hive-metric, the one reason its declaration deliberately differs. Why an HTTP 200 is the failure that matters, and what a stderr-reporting CLI would cost, are the PR's and the follow-up issue's job, not the manifest's. |
||
| .. | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
hive-metric
A tiny CLI that pushes a single labeled metric to the OTEL collector, then exits. Built on the OpenTelemetry Rust SDK with the OTLP HTTP/JSON exporter.
When to use it
For emitting a one-off counter or gauge from a shell script or systemd unit without embedding an OTEL SDK in the caller — the harness and various hive scripts use it to record per-agent metrics.
Usage
hive-metric <name> <value> [--type counter|gauge] [--labels key=value ...]
Standard OTEL environment variables are read automatically by the SDK:
OTEL_EXPORTER_OTLP_ENDPOINT— collector URL (required)OTEL_EXPORTER_OTLP_HEADERS— auth headers (Key=Value,...)OTEL_RESOURCE_ATTRIBUTES— resource labels (k=v,...)
The harness populates all of these per-agent when
services.hyperhive.otel.enable = true. See docs/observability.md for the
collector setup and the metrics hyperhive exports.