docs: reword reports/events union without old/new framing

2026-09-05 11:56:50 +10:00
parent 4af15041b3
commit 1179d4567e
1 changed files with 6 additions and 6 deletions
@@ -54,12 +54,12 @@ unknown fields survive untouched.
  - A node present in only one backend always appears (falls back to whichever
    backend actually returned facts for it).
 - **`/reports`, `/events`** — **union**, not a per-node winner. Reports are
-  immutable history, so a node that moved between PuppetDBs legitimately has
+  immutable history, so a node's reports can legitimately exist in more than one
-  reports in both and both belong in the merged view. Reports dedupe
+  backend and all of them belong in the merged view. Reports dedupe on `hash`;
-  on `hash`; events, which carry no id of their own, dedupe on the verbatim
+  events, which carry no id of their own, dedupe on the verbatim record (a node
-  record (a node briefly reporting to both PuppetDBs stores identical records in
+  reporting to more than one backend stores identical records in each). Records
-  each). Records the merge cannot key — `extract`/`group_by` aggregate rows — are
+  the merge cannot key — `extract`/`group_by` aggregate rows — are never
-  never deduped, so every backend's rows pass through even when byte-identical;
+  deduped, so every backend's rows pass through even when byte-identical;
  summing those aggregates across backends is not implemented yet.
 ### Paging and ordering on the merged endpoints