mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-24 04:33:17 +00:00
rcourtman
fa02fcf5c9
While a standalone agent stays offline across a restart (up to the 72-hour continuity window), every canonical read-state lookup adds it back from host continuity by building a whole registry clone (`readStateWithRecords`). Alert evaluation makes one lookup per resource per poll, so in that state each poll rebuilt the registry once per resource. Each lookup also called `GetLiveHostsSnapshot` twice, and that went through `State.GetSnapshot()`, deep-copying every VM and container just to return the hosts. **Changes** - **Overlay cache.** The adapter keeps the last continuity overlay, keyed by: - the registry pointer; - `LastRebuiltAt` (every replace and in-place supplemental ingest updates it); - a fingerprint of the requested records. The fingerprint leaves out `Resource.UpdatedAt`, which `resourceFromHost` stamps with `time.Now()` at build time. It reuses the overlay for at most 2 s, because the overlay evaluates source staleness when it is built. The live adapter is never mutated. - **Hosts-only copy.** `GetLiveHostsSnapshot` now copies only hosts, through the existing `State.GetHosts()`. The result is identical, because `GetSnapshot` sets `Hosts: cloneHosts(s.Hosts)`. This also removes a full state copy from each agent report (`ApplyHostReport`), each config fetch and every other caller. - **Single host copy per lookup.** `readStateWithStandaloneHostContinuity` takes the host list once instead of twice. **One read-state lookup** with one offline standalone agent (synthetic, 8-node clusters, pulse-dev): | Resources | main | this PR | |---|---|---| | 130 | 3.0 ms / 1.9 MB | 13 µs / 10 KB | | 520 | 15.9 ms / 11.8 MB | 25 µs / 29 KB | | 1,040 | 41 ms / 28 MB | 39 µs / 54 KB | | 2,080 | 136 ms / 95 MB | 74 µs / 104 KB | **Tests.** Each fails when its mechanism is reverted. - `TestHostContinuityOverlayReusedWithinRegistryGeneration`: reuse within a generation, including records rebuilt with a fresh `UpdatedAt`; rebuild after a new generation or different records; the 2 s age bound; and no mutation of the live adapter. - `TestStandaloneHostContinuityReadStateReusedAcrossLookups`: end to end through `GetUnifiedReadStateOrSnapshot` with a real continuity store. - `TestGetLiveHostsSnapshotCopiesOnlyHosts`: 1 host with 1,000 VMs must not allocate per guest. The old path made 1,010 allocations. **Verification on pulse-dev:** `internal/unifiedresources`, `internal/monitoring`, the `internal/api/...` subpackages and `cmd/pulse-control-plane` 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.