mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-14 08:10:26 +00:00
rcourtman
b262f24c54
The remaining scroll hitch on large estates was the realtime websocket tick: every few seconds a delta landed mid-gesture and blocked the main thread for 200-560ms. The scroll path itself was already clean after the windowing fixes, so the tick was the one thing still hitting the wheel. Mid-gesture ticks now cost ~1ms: the resource delta queues unapplied in arrival order (even the baseline patch walks the whole estate), and the reporting projection plus the lastUpdate tick token defer latest-wins alongside it. Holding the token matters as much as holding the data — it is what unified resource projections and workload remaps key on, so deferring it keeps every downstream consumer quiescent through the gesture. Everything drains as one coalesced batch at scroll idle, through the same deferral set and flush the hidden-tab path uses. Ordering and lifecycle guards: a non-empty queue keeps queueing so deltas never apply out of order, hidden-tab ticks drain the queue before applying in place, a full snapshot supersedes and clears the queue, and connection resets drop all pending deferral state. Alert application stays live mid-gesture. Verified on the 50-node/929-guest mock estate: zero websocket long frames across 16-20s continuous scrolls (previously one 200-560ms block per tick), one coalesced flush ~300-450ms after gesture end, and the Last refresh footer still advancing on desktop and narrow viewports. This is a scheduling boundary, not a cost reduction: the per-tick reconciliation cost itself remains owned by the resource-payload-static-metadata coverage gap.
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.