Skip to content

armgit / Pulse

Public Imported from GitHub
0

Real-time monitoring dashboard for Proxmox VE, PBS, Docker, Kubernetes, TrueNAS and vSphere. Self-hosted, with alerts for failed backups, full disks, unhealthy containers and offline nodes.

Integrate reviewed Patrol manual-rule reversal

pulse-triage[bot]c3c9a86b8c35
diff --cc docs/release-control/v6/internal/subsystems/api-contracts.md
index fdea524f6a,28dff957bb..f99a22e1f8
--- a/docs/release-control/v6/internal/subsystems/api-contracts.md
+++ b/docs/release-control/v6/internal/subsystems/api-contracts.md
@@@ -20,26 -20,25 +20,45 @@@
## Purpose
+### Existing disk History keeps native thermal fallback reachable
+
+The authenticated disk History endpoint supplements a missing or shallow
+`smart_temp` series even when independent I/O metrics already exist in the
+persistent store. Single-metric and the drawer's all-metric requests use the
+same monitor-owned native/local selection. Only a broader series (or more
+actual samples at equal span) replaces the thermal series; unrelated stored
+values and min/max bounds stay unchanged. Samples stay within the issued
+window and use the existing aggregation and fallback-source wire contract.
+Complete local coverage makes no native history call. Store errors remain
+HTTP 500 rather than being concealed by native fallback.
+
+`TestTrueNASDiskHistoryAuthenticatedRoute` traverses the real authenticated TLS
+client, provider, tenant poller, monitor and router using declared appliance
+responses and ordinary store writes. It covers nil store, I/O-only store, a
+single thermal row, complete local coverage, store errors, token scope, tenant
+binding and revocation. It preserves original Celsius samples/timestamps and
+independent I/O, not synthetic temperature padding or CPU substitution. This
+is connected source proof, not an installed appliance or containing release.
+
+ ### Confirmed Patrol rule operations preserve tenant context — issue #2528
+
+ The manual-rule confirmation presents the returned exact ID and scope before a
+ keyboard-scrollable reason; the readable header and Cancel/Remove footer remain
+ separate from long data. This does not truncate the stored reason or change
+ authorised pre-read, one DELETE, readback or uncertainty handling.
+
+ The frontend consumes the existing GET/DELETE suppression endpoints without a
+ wire or permission change. The optional client expectedOrgID pins the request
+ header and checks context before and after CSRF preparation; retry:false
+ disables auth, invalid-organisation, CSRF and rate-limit retries for this flow.
+ Other callers retain their defaults. Current auth, scope and CSRF checks remain
+ authoritative; an abort or mismatched context stops dispatch. The suppression
+ client rejects malformed or duplicate rows, accepts the existing empty nil
+ slice, and only deletes a rule_ identity with explicit manual origin and no
+ finding/dismissal attribution. Transport success alone is not removal: the UI
+ must read the same collection back and establish exact-ID absence.
+
+
### Organisation deletion retains data after incomplete monitoring shutdown
Authenticated organisation-owner deletion waits for tenant-loop exit and sealed