mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-24 12:42:49 +00:00
rcourtman
ac643e2bde
Each outdated Pulse Agent on Settings › Infrastructure was flagged twice: an amber **Agent update** badge, plus a second-line **Version behind** note. The band also counted every outdated agent as needing attention. On a mock estate it read "11 systems needs attention", and all 11 were version lag. - **Version lag is maintenance.** Version behind and Update available are now maintenance signals. The badge, which opens Agent Doctor, carries them, so they never become the row's problem line and don't count toward needs attention. The Manage drawer still lists every fleet signal. - **Real update problems still show.** A failed update and auto-update switched off remain row problems, since each needs a different action. - **Problems can't hide behind the cap.** A row's problem is now picked from all its visible signals before the three-highlight cap, and problems rank ahead of maintenance. A second attached agent's failed update can no longer fall behind another agent's version lag. - **The band** says how many agent updates are available, in a neutral tone. "Systems need" and "hosts have" now agree in number. - **Column widths.** The Actions column is wide only when a row shows an install button beside Manage, and Health gets 27% of the table. The Health cell now keeps the status, the badge and the last-seen time on one line. On main, the last-seen time was cut to "18s a…". Verification: - At 1280, 1440 and 1920px the table has 16 rows and no clipped cells. Main has 27 rows (including 11 problem lines), with 11 and 6 clipped cells at 1280 and 1440px. - The phone card layout shows no Version behind lines. - Re-measured after rebasing onto the shared Table change in #2524. The receipt is included.
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.