mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-24 12:42:49 +00:00
rcourtman
f9ce06123a
Two small user-lens fixes from a live pass over Machines. **Outdated-agent notice wording** Machines told users to update "for the latest agent command support and agent-managed platform detail". Proxmox, TrueNAS and vSphere used similar internal phrasing: "agent-contributed Proxmox node detail and command support", "agent-contributed TrueNAS system detail and command support" and "in-guest telemetry and command support". All four now read "Update them to v4.26.0 for the latest fixes and machine details", or node, system or VM details. The notice does not promise Patrol actions or command support. It selects hosts by agent version alone, and command execution is a separate setting that the upgrade command preserves, so an update neither grants nor removes it. **CPU count** A machine's CPU cell reads "22% (18)", and nothing explained the 18: the hover panel listed only Usage and Load (1m). The shared CPU bar's hover panel now leads with "CPUs 18". The number is logical CPUs on a host and configured vCPUs on a guest, so "Cores" would be wrong on hyperthreaded machines. **Verification** - **Live, private mock stack:** - The Machines and Proxmox notices read the new wording. TrueNAS and vSphere have no outdated agents in the mock, so the updated page contract tests cover them. - Hovering a machine's CPU bar shows "CPUs 18" above Usage and Load. - **Tests:** 1,236 tests pass across the touched surfaces, including two new hover tests (row present, row omitted when the count is unknown). - **Review:** a second reviewer caught that "Patrol actions" overclaimed what an update brings, and that "Cores" mislabels logical CPUs and vCPUs. Both are fixed.
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.