Files
pulse/docs
rcourtman cdae811bb7 Chart Net and Disk I/O in the row history lens
Hovering a guest row swapped CPU, memory and disk for history
sparklines but left Net I/O and Disk I/O as static numbers, although
they are the jumpiest readings in the row and the hover request
already returns their series. The lens now charts all five cells on
one synchronized cursor.

I/O charts, on hover and in Trends, keep a compact current pair
beside the chart (↓3.3M ↑2.2M, R1.4M W826K) instead of hiding the
rates in a tooltip; the glyphs use the series colours so the pair is
also the legend. Rate sparklines get a 100 KiB/s scale floor so an
idle guest's few-KB/s chatter no longer draws the same full-height
spike as a busy one.

GuestRow now builds every sparkline from accessors. Each live
snapshot used to remount the lens and Trends charts, dropping an open
scrub tooltip; an open tooltip also re-reads the current series
instead of holding the values from the last mouse move.
2026-10-06 20:33:10 +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.