mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-25 21:20:00 +00:00
rcourtman
eeda20c0dd
Keep monitoring readings, trusted connections and recovery guidance reliable when observations are stale, guest responses are incomplete or agent recovery is interrupted. Qualified source: `b6e56c5baa2ad995264faa80877543300bc10273`. All nine [required source checks](https://github.com/rcourtman/Pulse/pull/2888/checks), the [native matrix](https://github.com/rcourtman/Pulse/actions/runs/39148879516) and [Core E2E](https://github.com/rcourtman/Pulse/actions/runs/39148879470) passed. Intel accounted for all 545 installer roots, with 532 passes, 13 explicit platform skips and no failures. Its remaining installer phase passed in 18m48s, followed by native agent build and execution. The matrix covers Linux x64/ARM64, macOS Intel/ARM64 and Windows x64 execution plus the FreeBSD cross-build contract. - Preserve reading provenance, measured zero, stored History and VM/LXC memory interpretation. Selected-agent staleness cannot renew a retained observation or invalidate independent provider readings. - Reject incomplete or foreign guest responses and retain saved certificate trust, scoped access, private installer input, native NAS teardown and bounded recovery guidance. - Keep initial Proxmox login within its caller and total client timeout while accepted-session renewal remains shared. Preserve the PBS owner's context outcome when cancellation races a response, prevent a cancelled fallback and reject late session publication. - Assert troubleshooting workflows and destinations semantically. Run every discovered Python safety control and native Go root independently with existing fixture, operation, root and job deadlines. Script-smoke and native verification share one control suite, including real compiled-Go failure, exit-zero, timeout and exact-selector controls. - Integrate current main while retaining selected-agent freshness, guest memory interpretation, native GNU prerequisites, API concurrency controls and both parents' subsystem contracts. Worker proof passed 113 focused frontend cases, API and guest-transport race checks, all 59 Python fixture controls, production frontend build and full frontend lint/types. The exhaustive worker installer inventory accounted for 551 roots: 535 passed and 16 explicitly skipped for platform reasons. The eight consolidated runner controls passed through the script-smoke harness and native Go wrapper. Authentication proof passed all 340 Proxmox tests, 108 PBS tests and the affected monitoring cancellation controls under the race detector. The new PBS test first failed all ten JSON/form cases on unchanged runtime, then passed with the correction. Status, ownership and normal commit checks passed. Browser proof uses production components and CSS with synthetic observations and endpoints. Drawer History passed at 1280×900, 1024×768 and 390×844. Private installation passed at 1280×900 and 390×900 in both themes. It covers stale/current/unknown readings, provider caveats, stored History and keyboard inspection, wrapped signing keys, token copy/dismissal and Last seen advancing without another lookup. Final screenshots were inspected, the source-bound receipt covers the combined runtime files, and owned browsers and servers were closed. Retain the [previous Frontend assertions](https://github.com/rcourtman/Pulse/actions/runs/38660106123/job/116179237804), [Intel timeouts](https://github.com/rcourtman/Pulse/actions/runs/39138980077/job/117709536519), [script-smoke integration failure](https://github.com/rcourtman/Pulse/actions/runs/39145479921/job/117728549560) and [PBS cancellation race](https://github.com/rcourtman/Pulse/actions/runs/39145479921/job/117729442632) with their diagnosed causes and corrected proof. The final matrix above qualifies the combined corrections. The [earlier advisory benchmark comparison](https://github.com/rcourtman/Pulse/actions/runs/39138980114/job/117709718583) reported three legacy history-filter regressions. A worker repeat reproduced one. Longer controls showed wide timing variation even between byte-identical binaries. The [45a82ea03ccomparison](https://github.com/rcourtman/Pulse/actions/runs/39145479921/job/117728549510) passed against a newer baseline. The [final comparison](https://github.com/rcourtman/Pulse/actions/runs/39148879492/job/117738375776) completed execution but failed on test-only empty/legacy filtering, 2.945 to 3.263ns, +10.82% (p<.001, ten samples). Production empty filtering improved 16.70%, interleaved filtering rose 2.96%, and history allocation counts were unchanged. The filter and benchmark sources are byte-identical across the final comparison. This does not establish a cause or performance closure. Artifact 12145720151 retains full paired samples, comparison and metadata. The overall Build and Test workflow is red from this advisory job while all nine protected required checks pass. The existing L1 reliability follow-up owns repeatability and attribution. No benchmark threshold, protected check or release gate changed. Main's benchmark/SLO test and documentation changes in PR3053 compose without conflict. The candidate benchmark artifact records synthetic merge c21333c676ac004935c9683027490203d8f869ea with treefa059ae37b, combining this head and main52b40fd611. A bounded worker composition proof also executed all three chart benchmark cases under the race detector with source hashes unchanged. Its SLO test explicitly skipped under the race detector, and one-iteration execution supplies no performance comparison. This proposal qualifies source delivery. Release inclusion, installed upgrade/recovery, guest thaw, fresh writes on every backed-up filesystem and workload liveness remain separate outcomes. Reliability keeps its existing priority. Recovery/change feature expansion stays deferred. Related to #1099, #2439, #2619, #2822, #2897, #2757, #2511, #2513, #1788, #2755 and #2140.
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.
Need help with a failure? Read the safe reporting guidance before sharing evidence. A second reproduction or diagnostics export is not required; keep the original evidence if another attempt could interrupt workloads or send duplicate notifications. GitHub reports and attachments are public: review them locally and keep credentials and private details out.
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.