swarm-controller: move OTEL deps to workspace level, drop jobq_metrics singleton
This commit is contained in:
parent
1f5a7b71ed
commit
621245306f
6 changed files with 81 additions and 67 deletions
|
|
@ -11,9 +11,8 @@ 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"] }
|
||||
# OTEL SDK, from the workspace base — see the root Cargo.toml's comment for
|
||||
# the blocking-client rationale shared by every OTEL-pushing crate.
|
||||
# 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
|
||||
|
|
@ -21,9 +20,6 @@ opentelemetry_sdk = { version = "0.32", features = ["metrics"] }
|
|||
# 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",
|
||||
] }
|
||||
opentelemetry.workspace = true
|
||||
opentelemetry_sdk.workspace = true
|
||||
opentelemetry-otlp.workspace = true
|
||||
|
|
|
|||
Loading…
Reference in a new issue