mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-24 12:42:49 +00:00
rcourtman
48b3d3586b
Every accepted agent report sends a websocket state invalidation, and each state broadcast rebuilds and diffs the full frontend state: | Resources | One broadcast (`BuildFrontendState` + JSON) | |---|---| | 130 | 7.5 ms | | 1,040 | 62 ms | | 2,080 | 132 ms | The hub's keyed snapshot adds about 10 ms per 1,000 resources. The hub coalesced invalidations with a 100 ms debounce that **restarted on every signal**. That caused two problems: - Reports spaced more than 100 ms apart (typical for agents on independent 30 s timers) each produced a full broadcast. With 200 agents that is roughly 3.4 broadcasts/s, about half a core whenever a browser is open. - Signals closer together than the window postponed the broadcast until they stopped. **Change: coalescing is now a throttle.** - The first invalidation after a quiet period still broadcasts after the 100 ms window. - Later invalidations for the same audience (all clients, or one tenant) replace the pending request without rescheduling it. - They broadcast no sooner than `defaultStateBroadcastInterval` (2 s) after that audience's previous broadcast. That caps broadcast work near 7% of a core at the same scale. 2 s matches the report-driven store refresh interval (#2242), so faster broadcasts mostly re-sent the same resources. Broadcasts are still skipped when no client is connected. **Tests.** Each fails with the old restart-on-signal, unspaced behaviour. - `TestStateBroadcastsSpacedByInterval`: the second broadcast waits for the interval and carries the latest of a burst; the burst produces only one broadcast. - `TestTenantStateBroadcastsSpacedByInterval`: the same for tenant broadcasts. - `TestStateBroadcastNotStarvedBySteadySignals`: signals every 10 ms against a 60 ms window still produce broadcasts. The old debounce produced none in 600 ms. **Verification on pulse-dev:** `internal/websocket` (existing coalescing tests unchanged), `internal/monitoring`, `pkg/server` and the `internal/api/...` subpackages pass. `TestServerInfoEndpointReportsDevelopment` fails in that source export with and without this change, because the export has no git checkout. Refs #2199
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.