gitea-mirror/Pulse
1
0
Fork 0
mirror of https://github.com/rcourtman/Pulse.git synced 2026-02-18 00:17:39 +01:00
Code Issues Packages Projects Releases Wiki Activity
Files
main
Pulse/docs/ZFS_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.2 KiB
Raw Permalink Blame History

💾 ZFS Pool Monitoring

Pulse automatically detects and monitors ZFS pools on your Proxmox nodes.

🚀 Features

  • Auto-Detection: No configuration needed.
  • Health Status: Tracks ONLINE, DEGRADED, and FAULTED states.
  • Error Tracking: Monitors read, write, and checksum errors.
  • Alerts: Notifies you of degraded pools or failing devices.

⚙️ Requirements

The Pulse user needs Sys.Audit permission on /nodes/{node}/disks (included in the standard Pulse role).

# Grant permission manually if needed
pveum acl modify /nodes -user pulse-monitor@pam -role PVEAuditor

🔧 Configuration

ZFS monitoring is enabled by default. To disable it:

# Add to /etc/pulse/.env (systemd/LXC) or /data/.env (Docker/Kubernetes)
PULSE_DISABLE_ZFS_MONITORING=true

🚨 Alerts

Severity Condition
Warning Pool DEGRADED or any read/write/checksum errors.
Critical Pool FAULTED or UNAVAIL.

🔍 Troubleshooting

No ZFS Data?

  1. Check permissions: pveum user permissions pulse-monitor@pam.
  2. Verify pools exist: zpool list.
  3. Check logs: journalctl -u pulse -n 200 | grep -i zfs.