mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-09-11 22:12:23 +00:00
rcourtman
7bac525af3
The 2026-08-25 frontend perf audit measured 21-31% idle main-thread saturation on phones (4x throttle, 50-node mock estate) with the dominant costs in the websocket tick pipeline rather than rendering. useUnifiedResources deep-unwrapped the entire resource store on every websocket tick in every realtime hook instance (1.7s per 20s idle window on the Alerts page alone). The realtime effect now skips the store read entirely when the tick's revision is already applied, and the merging instance unwraps only the subtrees the delta merge will clone: flagged ids, host-merge members, and ids absent from the shared cache. mergeCanonicalResourceDeltaSnapshot re-cloned and re-canonicalized every agent resource on every tick because a host-merge group could change without its surviving member being flagged. Host-key groups now refresh only when a member id is in the delta; a flagged id absent from the incoming snapshot (removal, or a partner a previous coalesce folded away) conservatively refreshes every group. useWorkloads rebuilt every row object each refresh, churning row identity estate-wide per metrics tick. Rows whose serialized form is unchanged now reuse the previous object via WeakMap-cached signatures, and refreshes that change nothing return the previous array identity. The joined signature cache field this replaces is removed. Remeasured (mobile 4x, dev attribution, 20s windows): Alerts-page tick unwrap 1713ms -> 200ms, Overview app busy -27%, workload signature cost -72%. Contracts for unified-resources, performance-and-scalability, and storage-recovery are amended to state the group-scoped coalesce refresh and lazy store-read obligations.
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.
- 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.