mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-24 12:42:49 +00:00
rcourtman
40ebce161a
Stacked on #2589 (the threshold-off fix). Until it merges this PR also
shows its two commits; the change here is the last commit, 7c8e9099a1.
A host-agent SMART disk temperature alert (`diskTemperature`, resource
`agent:<host>/disk_temp:<device>`) stayed active for about a day after
its disk left the agent's report (removed, replaced, or a renamed device
path). `CheckHost` only evaluates disks it still lists, and
`shouldPreserveAlertOutsideNodeCleanup` exempts `agent:` alerts from
node cleanup, so only the 24-hour stale-alert sweep resolved it.
What changes:
- `CheckHost` records every disk a non-empty SMART list reports. A disk
holding an alert or a pending threshold run that is missing from three
consecutive non-empty reports has its alert cleared and its pending run
dropped (`cleanupHostDiskTemperatureAlerts`). The count restarts when
the disk is reported again, because the Windows, FreeBSD and
controller-multiplexed Linux collectors drop a disk whose probe fails.
- An empty SMART list holds every alert. The agent omits the list when
SMART collection fails or is unsupported (`collectSMARTData`).
- A listed disk in standby, or with no temperature (a failed Linux probe
lists the disk identity-only), holds its alert. Neither reading shows
the disk cooled, and SMART health alerts already hold through standby.
- Turning the threshold off, or removing the agent, now also drops the
host's pending disk temperature runs and absence counts.
`TestCheckHostClearsDiskTemperatureAlertWhenDiskLeavesSMARTReport`
covers removal, rename, the three holds, the restarted count, and the
pending-run and count cleanup. Each case was checked against a mutation
that disables its mechanism.
Pulse documentation
Start here for installation, platform setup, security, operations, and Pulse Intelligence. Commands, configuration keys, image names, API fields, and product identifiers remain untranslated in localized guides.
Start here
- Install Pulse — signed Proxmox/Linux installation, Docker, Docker Compose, Kubernetes, and first-run setup.
- Production deployment and security — least-privilege Proxmox setup, root-agent boundaries, discovery, supply-chain verification, plan limits, scale evidence, and a rollout checklist.
- Upgrade from Pulse v5 — migration prerequisites, rollback, agent continuity, and post-upgrade checks.
- Releases and update channels: choosing Stable or Preview, beta and RC expectations, and how releases are tested and promoted.
- Configure Pulse — authentication, notifications, discovery, retention, and system settings.
- Deployment models — data locations, lifecycle, and differences between supported deployment paths.
- Troubleshooting and FAQ — common failures, diagnostics, and operator questions.
Localized getting started guides: Deutsch · Español
Platforms and agents
- Proxmox Backup Server
- Proxmox Mail Gateway
- Docker and Podman
- Kubernetes and Helm
- TrueNAS SCALE and CORE
- Unified Agent
- Agent security
- VM disk monitoring
- ZFS monitoring
- Temperature monitoring
VMware vSphere support is early access. Current builds expose dedicated vSphere inventory and recovery context, but operators should validate the integration against their own vCenter before production use.
Monitoring and operations
- Metrics history
- Recovery data
- Webhooks
- Automatic updates
- Centralized agent management (Pro)
- Operational trust model
- Current product screenshots
Pulse Intelligence
- Assistant, Patrol, and external-agent overview
- Patrol modes and safety
- Assistant safety model
- External agent HTTP and MCP substrate
Patrol watch-only analysis is available on Community with a local model or the operator's own provider. Investigation and governed fixes require the relevant Pulse Pro capabilities.
Security, privacy, and access
- Production deployment and security
- Security review scope
- Authentication and credential storage review packet
- Security guide
- Privacy and telemetry disclosure
- OIDC and SSO
- Proxy authentication
- Role-based access control (Pro)
- Audit logging (Pro)
- Reverse proxy configuration
- Code-signing policy
Plans and managed access
- Community, Relay, and Pro capabilities
- Relay and Pulse Mobile handoff
- Multi-tenant organizations (Enterprise/custom)
- Provider-hosted MSP operations (request-assisted)
Pulse Cloud is not generally available. Ordinary self-hosted Pulse remains the primary installation path; MSP and Enterprise access are explicit commercial paths rather than defaults in self-hosted setup.
Development and reference
Detailed design notes and dated migration specifications may remain in this directory for maintainers, but they are not operator setup guides unless they are linked from the sections above.
Previous versions and migrations
- Upgrade from v4 to v5
- Retired unified-navigation migration — historical context only; current Pulse uses platform-shaped navigation.
- Move a Pulse installation
Found a bug? Use the issue forms. For setup questions, use GitHub Discussions.