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.

Incorporate batch-start upstream alert configuration repair

pulse-triage[bot]34b924429b9a
diff --cc docs/release-control/v6/internal/subsystems/agent-lifecycle.md
index b89f6a8ace,629fa45621..478dfd2d9a
--- a/docs/release-control/v6/internal/subsystems/agent-lifecycle.md
+++ b/docs/release-control/v6/internal/subsystems/agent-lifecycle.md
@@@ -3755,26 -3690,14 +3755,34 @@@ Agent` secondary handoff against the li
## Current State
+Notification destination edits in the shared `internal/api/` subtree preserve
+only submitted masked values, honour neighbouring explicit map edits/removals
+and reject unrecoverable masks before publication. Restored custom-field
+credentials remain masked in the response. This is not an agent token rotation,
+identity change, installer permission or enrollment operation; those boundaries
+remain unchanged. The notification API's encrypted edit/reload and delivery
+controls cover this shared configuration-write boundary.
+
+### Disk History supplementation does not change agent lifecycle
+
+The disk History handler can replace a shallow API-backed thermal series with
+monitor-selected native history even when stored I/O exists. This read does
+not enrol, refresh, remove or grant an agent; it changes no agent identity,
+helper profile, report completeness or missing-series handling. Ordinary
+agent-backed stored metrics remain preferred when coverage is sufficient.
+The authenticated native-route control covers the store/native boundary.
+
+
+The partial-result path no longer discards every successful row when another guest fails. The helper remains in its private network on every platform; pmxcfs abstract IPC is still unavailable there on the reported PVE estate (#2511). That defect is not fixed by the partial protocol (#2513), and API monitoring remains the safe existing alternative. The earlier host-network proposal is not part of this implementation.
+
+ ### Alert settings saves do not touch agent lifecycle
+
+ `PUT /api/alerts/config` in `internal/api/alerting/alerts.go` now keeps stored
+ values for the top-level keys a client leaves out. Agent alert defaults
+ (`agentDefaults`) follow the same rule as every other key; enrollment,
+ reporting leases, commands and agent removal are unchanged.
+ `internal/api/alerting/alerts_test.go` pins the handler.
+
### VM guest execution admission (backup precaution)
`AgentRegisterPayload.guest_exec_guard_version` is optional; version 1 on a