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.
Go aialertsdashboarddockerdocker-monitoringgohomelabinfrastructure-monitoringkubernetesmonitoringmspproxmoxproxmox-backup-serverproxmox-mail-gatewayproxmox-veself-hostedtruenastypescriptvspherewebhooks
Preserve monitoring repairs with current demo and disk identity safeguards
pulse-triage[bot]2c02eba64b8d
diff --cc docs/release-control/v6/internal/subsystems/storage-recovery.mdindex 20770a54ff,1a55c2d23c..a0245b7b9d--- a/docs/release-control/v6/internal/subsystems/storage-recovery.md+++ b/docs/release-control/v6/internal/subsystems/storage-recovery.md@@@ -6932,8 -6896,13 +6941,19 @@@ The performance report and reporting rutest before tabulating a disk temperature. That changes only which held value areport shows, not any storage or recovery path.+The handler likewise withholds the live point for host agent, Proxmox node,+guest, integration host, Docker host and app container rows it judges to have+stopped reporting, or answers a lapsed linked agent from its node row. It reads+only snapshot status and the registry's per-source sightings, and writes+nothing.+++ ### Demo write guard ignores websocket upgrade headers++ `internal/api/demo_middleware.go` no longer exempts every request carrying+ `Upgrade: websocket` from the demo read-only guard. On a `DEMO_MODE` instance a+ `POST`, `PUT`, `PATCH` or `DELETE` with websocket handshake headers is now+ judged like any other write: outside the login, logout, AI execute and OIDC+ allowlist it gets the generic demo `403`, or `404` on a hidden route, and that+ includes config import at `/api/config/import`. HTTP/1.1 websocket handshakes+ are `GET` requests and still connect. No storage, retention, backup, migration+ or recovery path is added or moved.