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
Track recovery and change gaps after reliability
rcourtman606acc0a2db1
diff --git a/docs/release-control/control_plane.json b/docs/release-control/control_plane.jsonindex 9de4f50dc7..db8fa2da99 100644--- a/docs/release-control/control_plane.json+++ b/docs/release-control/control_plane.json@@ -89,7 +89,7 @@"profile_id": "v6","kind": "feature","status": "planned",- "summary": "Post-GA active development runs on main and promotes proactive Pulse Intelligence, policy-aware data governance, resource-change intelligence, action-governance, fleet-governance, agent-operable infrastructure onboarding, continuous discovery reconciliation, and agent-ready operations contract proof after the monitoring-first v6 floor; Patrol is the detection and investigation engine, Assistant is the contextual explanation, approval, and governed action surface, and agent-ready proof is API/CLI-first with MCP only as an adapter over canonical contracts. The planned product priority is a coherent Patrol-to-Assistant customer journey: explain the selected issue from current evidence, preserve governed approval and verification, and qualify useful outcomes for unhealthy services, backup or capacity risks, and supported VM or LXC actions before claiming broad Pulse Pro value.",+ "summary": "Post-GA active development runs on main and promotes proactive Pulse Intelligence, policy-aware data governance, resource-change intelligence, action-governance, fleet-governance, agent-operable infrastructure onboarding, continuous discovery reconciliation, and agent-ready operations contract proof after the monitoring-first v6 floor; Patrol is the detection and investigation engine, Assistant is the contextual explanation, approval, and governed action surface, and agent-ready proof is API/CLI-first with MCP only as an adapter over canonical contracts. The planned product priority is a coherent Patrol-to-Assistant customer journey: explain the selected issue from current evidence, preserve governed approval and verification, and qualify useful outcomes for unhealthy services, backup or capacity risks, and supported VM or LXC actions before claiming broad Pulse Pro value. Once v6-release-reliability explicitly yields priority, pick up recovery and change investigation through the existing L15 and L19 follow-ups and docs/release-control/v6/internal/RECOVERY_AND_CHANGE_INVESTIGATION_PLAN.md. Within that scope, the sequence is backup task outcomes, incident-focused change investigation, workload protection assessment, safe configuration diffs, then demand-dependent recovery-test evidence. Activate one bounded slice through the normal target and demand process rather than starting the whole sequence.","completion_rule": "manual","proof_scope": "none"},diff --git a/docs/release-control/v6/internal/RECOVERY_AND_CHANGE_INVESTIGATION_PLAN.md b/docs/release-control/v6/internal/RECOVERY_AND_CHANGE_INVESTIGATION_PLAN.mdindex 4d06416831..7162096142 100644--- a/docs/release-control/v6/internal/RECOVERY_AND_CHANGE_INVESTIGATION_PLAN.md+++ b/docs/release-control/v6/internal/RECOVERY_AND_CHANGE_INVESTIGATION_PLAN.md@@ -1,8 +1,9 @@# Recovery confidence and change investigation plan-Status: PROPOSED POST-RELIABILITY PLAN. Audit and sequencing only. Implementation remains unscheduled under the existing L15 and L19 follow-ups and demand ledger. This document does not activate a lane, change the reliability target, or add a release gate.+Status: TRACKED POST-RELIABILITY PLAN. Audit and sequencing only. The existing planned product target, L15 and L19 follow-ups, and demand ledger link to this sequence. Implementation remains unscheduled until reliability explicitly yields priority. This document does not activate a lane, change the reliability target, or add a release gate.Reviewed: 2026-10-17+Roadmap tracking updated: 2026-10-18Source baseline: `8f10dfa9438151db41ea01ccf19e58b669601e96`Pulse should first make recovery evidence and nearby changes easier to act on. The strongest first investment is the already-requested cross-system backup task timeline. Follow that with an accessible incident-focused change investigation flow, then a consistent explanation of workload protection and its objectives. Full recovery orchestration is a later product decision.@@ -150,9 +151,18 @@ Begin with evidence from an explicit external or operator-run test attached to t## Governance and activation-L15 remains tracked by `storage-recovery-post-rc-hardening`. L19 remains tracked by `resource-change-intelligence-post-rc-hardening`. L20 governs any later expansion of executable actions. Their existing bounded-residual states remain unchanged by this audit.+The existing roadmap owns pickup of this sequence:-When reliability work is explicitly ready to yield priority, activate one bounded slice through the existing target and demand process. Reconcile the relevant ledger entry and contract, reserve its claim, and name its source owner and proof obligations before implementation. This proposed sequence is not evidence that the reliability target has completed and is not independent authority to start every item.+| Canonical record | Tracked scope |+| --- | --- |+| Planned target `v6-product-lane-expansion` in [control_plane.json](../../control_plane.json) | Links this plan for consideration after `v6-release-reliability` explicitly yields priority. The reliability target remains active. |+| L15 follow-up `storage-recovery-post-rc-hardening` in [status.json](status.json) | Orders 1, 3 and 5, with the existing task timeline contract and a separate decision before recovery-test execution. |+| L19 follow-up `resource-change-intelligence-post-rc-hardening` in [status.json](status.json) | Orders 2 and 4, starting with access to retained history before richer configuration diffs. |+| Existing demand entries in `pulse-pro/FEATURE_REQUESTS.md` | Cross-system backup task timeline and outcomes links order 1. Infrastructure lifecycle event timeline distinguishes the bounded L19 investigation work from its broader, still-watching request. |++L15 and L19 keep their existing planned follow-ups and bounded-residual lane states. L20 governs any later expansion of executable actions. Demand statuses and signal counts are unchanged. The audit and roadmap direction are not additional independent customer signals.++When reliability work is explicitly ready to yield priority, activate one bounded slice through the existing target and demand process. Reconcile the relevant ledger entry and contract, reserve its claim, and name its source owner and proof obligations before implementation. This tracked sequence is not evidence that the reliability target has completed and is not independent authority to start every item.## Browser audit evidencediff --git a/docs/release-control/v6/internal/status.json b/docs/release-control/v6/internal/status.jsonindex 37a5253116..8ff3bd12a2 100644--- a/docs/release-control/v6/internal/status.json+++ b/docs/release-control/v6/internal/status.json@@ -9470,7 +9470,7 @@},{"id": "storage-recovery-post-rc-hardening",- "summary": "Track broader storage health UX polish and recovery timeline hardening beyond the current RC floor, including additional filter coherence edge cases and storage panel presentation improvements.",+ "summary": "Track broader storage health UX polish and recovery timeline hardening beyond the current RC floor, including additional filter coherence edge cases and storage panel presentation improvements. Post-reliability recovery priorities are orders 1, 3 and 5 in docs/release-control/v6/internal/RECOVERY_AND_CHANGE_INVESTIGATION_PLAN.md: cross-system backup task outcomes under docs/BACKUP_TASK_TIMELINE_CONTRACT.md, one understandable workload protection assessment, then demand-dependent retained recovery-test evidence. Pick up through planned target v6-product-lane-expansion only when v6-release-reliability explicitly yields priority. Reconcile the existing task-timeline demand entry and stable-delivery prerequisite before activation. Recovery-test execution remains a separate L20 admission decision.","owner": "project-owner","status": "planned","recorded_at": "2026-03-14",@@ -9553,7 +9553,7 @@},{"id": "resource-change-intelligence-post-rc-hardening",- "summary": "Track broader resource-change intelligence hardening beyond the current canonical timeline and relationship-map floor, including surfaced cross-resource timeline IA, enterprise correlation depth, and investigation workflows that promote relationship-aware timelines from backend foundation into deeper operator workflows.",+ "summary": "Track broader resource-change intelligence hardening beyond the current canonical timeline and relationship-map floor, including surfaced cross-resource timeline IA, enterprise correlation depth, and investigation workflows that promote relationship-aware timelines from backend foundation into deeper operator workflows. Post-reliability change priorities are orders 2 and 4 in docs/release-control/v6/internal/RECOVERY_AND_CHANGE_INVESTIGATION_PLAN.md: explicit incident-focused access to retained history with preserved resource/time context and continuation, then safe provider configuration diffs on canonical change records. Pick up through planned target v6-product-lane-expansion only when v6-release-reliability explicitly yields priority. The broader infrastructure lifecycle timeline retains its existing demand-ledger threshold.","owner": "project-owner","status": "planned","recorded_at": "2026-04-25",