mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-24 12:42:49 +00:00
rcourtman
0abe518219
Every accepted agent report refreshed the canonical resource store, and every refresh covers the whole estate, so refresh work grew with agent count × estate size (#2199). #2235 made each pass linear and cheaper. This PR bounds how many passes reports can trigger. **Behaviour.** Accepted host, Docker and Kubernetes reports, including rejected-report liveness, refresh through `refreshUnifiedResourceStoreAfterAgentReport`: - The first report after a quiet window is published before its handler returns, the same as today. - Reports within 2 s of the previous refresh fold into one trailing refresh at the window's end. It reads the latest state and broadcasts it to websocket clients. - 2 s matches `readPathRegistryFreshness`, the staleness the read paths already accept. - Agent removal and host-agent evaluation still refresh immediately, so removed inventory retires at once. - `Monitor.Stop` cancels a pending trailing refresh and waits for a running one before closing stores. - Monitors built without `New` keep a zero window and refresh on every report. **Cost bound.** At 2,080 resources one refresh costs about 82 ms (after #2235). 200 agents reporting every 30 s drive 6.7 refreshes/s, roughly 55% of a core; coalesced, reports trigger at most one refresh per 2 s, about 4%, however many agents report. **Contract change.** The agent-lifecycle contract promised that an accepted report is visible when its handler returns. It is now visible within the 2 s window. The founder approved that trade on 24 September 2026, and the contract records it. **Tests** - `TestAgentReportRefreshFoldsReportsWithinWindow`: the leading report is published synchronously; a burst inside the window is deferred; one trailing refresh publishes the burst's latest value; after a quiet window the next report is synchronous again. It fails when the throttle is removed. - `TestStopCancelsPendingAgentReportRefresh`: fails if stop does not cancel the pending refresh. - The issue-1753 end-to-end test posts two reports back to back, so it now waits for the published rows instead of reading them at once. **Verification on pulse-dev** - `internal/monitoring` runs in 112 s against 107 s on #2235's head. No test is slower by more than 1.2 s. - `internal/unifiedresources`, `internal/websocket` and `internal/api/...` 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.