Files
Pulse/docs/VM_DISK_MONITORING.md
rcourtman 2b48b0a459 feat: add --kube-include-all-deployments flag for Kubernetes agent
Adds IncludeAllDeployments option to show all deployments, not just
problem ones (where replicas don't match desired). This provides parity
with the existing --kube-include-all-pods flag.

- Add IncludeAllDeployments to kubernetesagent.Config
- Add --kube-include-all-deployments flag and PULSE_KUBE_INCLUDE_ALL_DEPLOYMENTS env var
- Update collectDeployments to respect the new flag
- Add test for IncludeAllDeployments functionality
- Update UNIFIED_AGENT.md documentation

Addresses feedback from PR #855
2025-12-18 20:58:30 +00:00

1.7 KiB

💾 VM Disk Monitoring

Monitor actual disk usage inside your VMs using the QEMU Guest Agent.

🚀 Quick Start

  1. Install Guest Agent:
    • Linux: apt install qemu-guest-agent (Debian/Ubuntu) or yum install qemu-guest-agent (RHEL).
    • Windows: Install virtio-win drivers.
  2. Enable in Proxmox:
    • VM Options → QEMU Guest Agent → Enabled.
    • Restart the VM.
  3. Verify:
    • Run qm agent <vmid> ping on the Proxmox host.
    • Check Pulse dashboard for disk usage (e.g., "5.2GB used of 32GB").

⚙️ Requirements

  • QEMU Guest Agent: Must be installed and running inside the VM.
  • Proxmox Permissions:
    • Proxmox 8: VM.Monitor
    • Proxmox 9+: VM.GuestAgent.Audit

🔧 Troubleshooting

Issue Solution
Disk shows "-" Hover over the dash for details. Common causes: Agent not running, disabled in config, or permission denied.
Permission Denied Ensure your Proxmox token/user has VM.GuestAgent.Audit (PVE 9+) or VM.Monitor (PVE 8).
Agent Timeout Increase timeouts via env vars if network is slow: GUEST_AGENT_FSINFO_TIMEOUT=10s.
Windows VMs Ensure the QEMU Guest Agent service is running in Windows Services.

Diagnostic Script

Run this on your Proxmox host to debug specific VMs:

curl -sSL https://raw.githubusercontent.com/rcourtman/Pulse/main/scripts/test-vm-disk.sh | bash

📝 Notes

  • Network Mounts: NFS/SMB mounts are automatically excluded.
  • Databases: Usage reflects filesystem usage, which may differ from database-internal metrics.
  • Containers: LXC containers are monitored natively without the guest agent.