Files
pulse/docs
rcourtman 28d5f44257 Judge disk risk only on a temperature collected now
Since #2593, a disk whose host agent stops reporting keeps its last
SMART temperature as a last-known value marked unavailable, and a disk
in standby keeps its pre-sleep reading the same way. The shared disk
risk assessment still fed that value into its temperature rule, so a
silent agent's frozen 72C made the disk read "Replace Now: Disk
temperature is 72C" with a warning status, while the temperature cell
beside it now says the reading is not current.

storagehealth.CollectedTemperature passes a temperature through only
when its collection state is available, or when the source predates
collection state. AssessPhysicalDisk, AssessHostSMARTDisk and the
registry's recompute from merged metadata use it, so a retained reading
stays on the resource as history but adds no temperature_high reason
and leaves the disk online. Health, wearout and SMART counters are
unchanged: they are durable evidence and keep judging as before.
2026-10-06 20:32:00 +01:00
..
2026-10-05 21:53:41 +01:00
2026-10-05 21:53:41 +01:00
2026-10-05 21:53:41 +01:00

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

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

Pulse Intelligence

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

Plans and managed access

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

Found a bug? Use the issue forms. For setup questions, use GitHub Discussions.