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
Keep independent Help and Backups contracts mergeable
pulse-triage[bot]3d4acf1b818c
diff --git a/docs/release-control/v6/internal/subsystems/frontend-primitives.md b/docs/release-control/v6/internal/subsystems/frontend-primitives.mdindex 6e61e9b505..2521a9cbd8 100644--- a/docs/release-control/v6/internal/subsystems/frontend-primitives.md+++ b/docs/release-control/v6/internal/subsystems/frontend-primitives.md@@ -20,24 +20,6 @@## Purpose-### Missing-filesystem help separates real capacity from container layers (28 October 2026)--The existing VM disk guide and Troubleshooting entry distinguish an attached-virtual disk, a real local filesystem under a container-data directory and an-intentionally excluded layer or remote mount. The version-specific v6.6.0 path-filter limitation is not an agent-installation diagnosis or a claim of repair.-Backup inclusion stays separate from capacity collection; deliberately excluded-disks stay excluded. Existing guest or already-linked-agent observations offer-an interim capacity view, not API recovery or complete monitoring.--`missingFilesystemGuide.test.ts` verifies the production Markdown renderer,-entry/target links, exact shipped mirrors, narrow-friendly prose instead of a-new table, source/time/privacy distinctions and the absence of new commands.-No remount, data move, service restart, new agent, guest probe or backup change-is prescribed. Backup safety retains precedence. Source-bound desktop/narrow-Docs interactions and inspected captures remain required; this is Help-maintenance, not a filesystem-admission fix, installed recovery or publication.-### Runtime alert controls describe only supported scope (28 October 2026)Container Runtime rows expose their existing Offline Alerts control, not an@@ -60,6 +42,24 @@ fulfilment of discussion #3432/#2107 whole-runtime-and-children demand, recipienproof, installed recovery or release availability.+### Missing-filesystem help separates real capacity from container layers (28 October 2026)++The existing VM disk guide and Troubleshooting entry distinguish an attached+virtual disk, a real local filesystem under a container-data directory and an+intentionally excluded layer or remote mount. The version-specific v6.6.0 path+filter limitation is not an agent-installation diagnosis or a claim of repair.+Backup inclusion stays separate from capacity collection; deliberately excluded+disks stay excluded. Existing guest or already-linked-agent observations offer+an interim capacity view, not API recovery or complete monitoring.++`missingFilesystemGuide.test.ts` verifies the production Markdown renderer,+entry/target links, exact shipped mirrors, narrow-friendly prose instead of a+new table, source/time/privacy distinctions and the absence of new commands.+No remount, data move, service restart, new agent, guest probe or backup change+is prescribed. Backup safety retains precedence. Source-bound desktop/narrow+Docs interactions and inspected captures remain required; this is Help+maintenance, not a filesystem-admission fix, installed recovery or publication.+### Coverage evidence remains inspectable without a pointerThe bounded Coverage preview includes undated source/state witnesses and a