From cf2b8c2ee4a8329dbcef5876275656fae6de62a1 Mon Sep 17 00:00:00 2001 From: iris Date: Sun, 20 Sep 2026 19:05:13 +0200 Subject: [PATCH] docs/scheduler/observability.md: clear write-good.Passive hits from the merge 2 real active-voice rewrites (per mara: main picked these up via a rebase+merge that landed after write-good.Passive went error-gate, never checked against the current rule): - "The datasource is told instead" -> nix/host-modules/swarm-grafana.nix tells the datasource instead. - "`value` is compared with `===`" -> the builder compares `value` with `===`. No suppressions, no content dropped. --- docs/scheduler/observability.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/scheduler/observability.md b/docs/scheduler/observability.md index 3bd06be8..bf63cd39 100644 --- a/docs/scheduler/observability.md +++ b/docs/scheduler/observability.md @@ -264,9 +264,9 @@ pipeline can fix: VictoriaLogs' OTLP ingester names the stored field `severity_text` unconditionally (v1.52.0, `app/vlinsert/opentelemetry/pb.go`), and its ingest parameters have no `_level_field` sibling to rename it with. -The datasource is told instead. `nix/host-modules/swarm-grafana.nix` -provisions the VictoriaLogs datasource with a `logLevelRules` entry per -severity in the table above, each matching `severity_text` against one of +`nix/host-modules/swarm-grafana.nix` tells the datasource instead, +provisioning it with a `logLevelRules` entry per severity in the table +above, each matching `severity_text` against one of those values — which is the plugin's way of saying "the level lives in this field." `logLevelRules` is the datasource plugin's own jsonData key and the only level-related one it has — there is no single "the level lives in field @@ -300,9 +300,9 @@ cleanly and the affected level button goes on returning zero rows: rules by it and only ever looks up `critical`, `error`, `warning`, `info`, `debug`, `trace`; `warn` and `fatal` are enum aliases that resolve to other spellings and match no group. -- `value` is compared with `===`, so it must be the severity text exactly as - stored: the uppercase OpenTelemetry short names `overwrite_text` writes in - `nix/journald-severity.nix`, not that table's lowercase keys. +- the builder compares `value` with `===`, so it must be the severity text + exactly as stored: the uppercase OpenTelemetry short names `overwrite_text` + writes in `nix/journald-severity.nix`, not that table's lowercase keys. ## Host-emitted container-resource metrics (hive-c0re)