docs: clear write-good.Passive hits in docs/scheduler/observability.md
4 genuine passive-voice rewrites (actor named, or the passive
construction replaced with an active imperative); 7 false positives
left untouched — predicate-adjective state/necessity descriptions
('is unchanged'/'is needed'/'is enabled' x2/'is unauthenticated'/
'is unaffected', same category as the already-established 'is
required') and one quoted-literal example string ('this hive is
gone').
This commit is contained in:
parent
78ebd7db3f
commit
63830e57b7
1 changed files with 6 additions and 4 deletions
|
|
@ -61,7 +61,7 @@ itself, so it could do all of the above _and_ use the token anywhere else. The
|
|||
collector removes the token and keeps the pipe. Agents are inside the trust
|
||||
boundary (`docs/trust-boundary/security.md`: capability = accepted risk), so an agent being
|
||||
able to _send_ is an accepted extension of that boundary — but it's not
|
||||
closed by this design, and nothing here should be read as closing it.
|
||||
closed by this design, and don't read anything here as closing it.
|
||||
|
||||
**The `agent` label is self-reported, and the hive→swarm authentication below
|
||||
doesn't change that.** Treat it as a convenience for grouping dashboards, never
|
||||
|
|
@ -280,8 +280,9 @@ records them (every turn, always).
|
|||
|
||||
## Hive-scoped metrics (hive-c0re)
|
||||
|
||||
Everything above is measured **per agent**, tagged with the hive it runs in.
|
||||
These three are measured per **hive**, and carry no `agent` label — so a hive
|
||||
hive-c0re measures everything above **per agent**, tagged with the hive it
|
||||
runs in. It measures these three per **hive** instead, and they carry no
|
||||
`agent` label — so a hive
|
||||
that hosts no agents still reports, and "this hive is quiet" is
|
||||
distinguishable from "this hive is gone." Select them with
|
||||
`{hive!="",agent=""}`.
|
||||
|
|
@ -348,7 +349,8 @@ hive-metric <name> <value> [--type counter|gauge] [--temporality delta|cumulativ
|
|||
`1` each time and the collector accumulates) or `cumulative` (this call
|
||||
reports the running total, which a stateless one-shot CLI can't track
|
||||
itself).
|
||||
- `--labels key=value` — extra per-data-point labels. May be repeated.
|
||||
- `--labels key=value` — extra per-data-point labels. Repeat the flag for
|
||||
more than one.
|
||||
`hive-metric` inherits the resource labels (agent, hive, swarm, service.name)
|
||||
automatically from `OTEL_RESOURCE_ATTRIBUTES` — don't re-specify them.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue