every hive runs its otel collector, and agents export to it by default
This commit is contained in:
parent
839efd1642
commit
13daf4c7dc
28 changed files with 245 additions and 303 deletions
|
|
@ -12,15 +12,15 @@
|
|||
//! sibling helper records why: two separate per-module mutexes serialise
|
||||
//! nothing against each other, and that produced a CI-only flake. The pair that
|
||||
//! motivated this one is `meta::tests` (which renders a flake from
|
||||
//! `HYPERHIVE_OTEL_*`) and `stats::otel_metrics::tests` (which asserts which
|
||||
//! variable enables the exporter) — different modules, same variable, same
|
||||
//! `HYPERHIVE_OTEL_EXTRA_RESOURCE_ATTRIBUTES`) and `stats::otel_metrics::tests` (which asserts which
|
||||
//! variable enables the exporter) — different modules, same process env, same
|
||||
//! binary.
|
||||
//!
|
||||
//! ⚠️ **A green local run is weak evidence for this class.** An agent container
|
||||
//! has the hyperhive variables ambient-set, so a losing race still finds a
|
||||
//! plausible value; the nix sandbox strips them, so there the race can delete a
|
||||
//! variable out from under another thread. Reproduce the sandbox shape with
|
||||
//! `env -u HYPERHIVE_OTEL_ENDPOINT cargo test -p hive-c0re`.
|
||||
//! `env -u OTEL_EXPORTER_OTLP_ENDPOINT cargo test -p hive-c0re`.
|
||||
|
||||
use std::sync::{Mutex, MutexGuard, PoisonError};
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue