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.
29 lines
1.1 KiB
TOML
29 lines
1.1 KiB
TOML
[package]
|
|
name = "hive-metric"
|
|
version.workspace = true
|
|
readme = "README.md"
|
|
edition.workspace = true
|
|
|
|
[[bin]]
|
|
name = "hive-metric"
|
|
path = "src/main.rs"
|
|
|
|
[dependencies]
|
|
anyhow.workspace = true
|
|
clap.workspace = true
|
|
# OTEL SDK — only used by this crate, so kept local rather than in workspace.dependencies.
|
|
opentelemetry = "0.32"
|
|
opentelemetry_sdk = { version = "0.32", features = ["metrics"] }
|
|
# Blocking (not async) reqwest client on purpose: the metrics SDK drives the
|
|
# OTLP push from a `PeriodicReader` background thread that has no Tokio runtime,
|
|
# 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",
|
|
"reqwest-blocking-client",
|
|
"reqwest-rustls",
|
|
] }
|