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
Real-time Proxmox, Docker and Kubernetes monitoring that finds what needs attention.
Pulse is a self-hosted monitoring workspace for Proxmox, Docker, Kubernetes, TrueNAS, physical and virtual machines, and early-access VMware vSphere environments. It combines live infrastructure state, history, alerts, recovery visibility, and scheduled health checks without requiring a conventional enterprise monitoring stack.
Why Pulse
- It watches between visits. Alerts and Pulse Patrol find failed backups, capacity pressure, restart loops, unhealthy containers, clock drift, and other problems that dashboards cannot surface when nobody is looking.
- It keeps each platform familiar. Proxmox, Docker, Kubernetes, TrueNAS, vSphere, and machines have dedicated views, backed by one shared resource model for search, alerts, history, and investigation.
- It stays operator-controlled. Credentials are encrypted at rest, API tokens are scoped, agent commands are disabled by default, and governed fixes require the configured policy and approval path.
Platform coverage
| Platform | Coverage |
|---|---|
| Proxmox VE, PBS, and PMG | Nodes, guests, storage, backups, replication, Ceph, mail gateways, and alerts |
| Docker and Podman | Hosts, containers, Compose projects, Swarm services, health, images, and updates |
| Kubernetes | Clusters, nodes, workloads, pods, services, storage, and events through the unified agent |
| TrueNAS SCALE and CORE | Pools, datasets, disks, snapshots, replication tasks, apps, VMs, and alerts |
| Linux, Windows, and macOS machines | Host health, filesystems, networking, temperatures, RAID, and availability through the unified agent |
| VMware vSphere | Early-access inventory, hosts, clusters, VMs, datastores, networks, snapshots, and recovery context; validate against your own vCenter before production use |
Platform pages keep storage and recovery information beside the infrastructure it belongs to. Alerts, Actions, and Patrol remain cross-platform views.
Patrol: monitoring that does rounds
Pulse Patrol runs scheduled checks across the current state and recent history of your infrastructure. Community installations can use a local model or their own AI provider for watch-only analysis. Pulse Pro adds investigation and policy-bound fixes with approval, verification, and an audit trail.
Pulse also includes an interactive Assistant and an MCP adapter for external clients such as Claude Code and OpenCode. Both sit on top of the same scoped inventory, metrics, alert, storage, and governed-action contracts.
Quick start
Choose an exact version from the latest release and keep that version pinned during installation.
Docker
docker run -d \
--name pulse \
-p 7655:7655 \
-v pulse_data:/data \
-e PULSE_DEPLOYMENT_METHOD=docker_run \
--restart unless-stopped \
rcourtman/pulse:vX.Y.Z
Open http://<your-ip>:7655 and follow the bootstrap-token setup. Docker host
monitoring is provided by the unified agent; the Pulse server container does
not need the Docker socket.
Proxmox LXC, Linux, and Kubernetes
The installer is signed. Verify install.sh against the pinned
pulse-installer key before running it:
export PULSE_VERSION=vX.Y.Z
curl -fsSLO "https://github.com/rcourtman/Pulse/releases/download/${PULSE_VERSION}/install.sh" &&
curl -fsSLO "https://github.com/rcourtman/Pulse/releases/download/${PULSE_VERSION}/install.sh.sshsig" &&
ssh-keygen -Y verify \
-f <(printf '%s\n' 'pulse-installer namespaces="pulse-install" ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMZd/DaH+BldzOkq1A8KVTcFk73nAyrE8aJOyf7i00jm pulse-installer') \
-I pulse-installer \
-n pulse-install \
-s install.sh.sshsig < install.sh &&
bash install.sh --version "${PULSE_VERSION}"
Paste the whole block: installation stops if either download or signature verification fails. Do not run the final command separately to bypass a failure.
The GitHub installer installs the Pulse server. Install and upgrade agents (including v5-to-v6 agent upgrades) with the per-host command generated under Settings → Infrastructure → Install on a host.
Do you need an agent?
Often not. Proxmox VE, PBS, and PMG are monitored through the Proxmox API with a read-only token, so no Pulse host agent is required. The generated setup script creates a privilege-separated monitoring user. Install the unified agent only where you want data the platform API cannot provide, such as host SMART health, temperatures, Docker hosts, or standalone machines.
API-only does not mean guest-agent-free. VM filesystem and memory requests through QEMU Guest Agent can share the channel used by freeze-enabled backups. Read-only permissions do not prove backup safety. Do not add permissions, enable or restart an agent, or send manual guest-agent probes during a backup, freeze or thaw. Use the existing backup safety precaution. Stopping Pulse also stops its monitoring and alerts. An OK backup task does not prove successful thaw.
The agent is operator-controlled by design. Command execution is off by
default, the local listener binds to localhost, and generated systemd units
ship hardened. On Linux, the installer's --least-privilege profile runs the
service as a dedicated non-root user, with optional scoped sudo grants for
the few collectors that need elevation. The
agent security model documents exactly what the
agent can and cannot do at each privilege level.
Important
GitHub release assets and
rcourtman/pulseimages are Community builds. Relay, Pro, and eligible legacy customers should use the private image or Linux archive provided by the Pulse download portal. Replacing a private Pro runtime with a public Community build removes its private runtime hooks.
Editions
- Community — self-hosted monitoring, seven days of metric history, core SSO, update alerts, and Patrol with your own provider or local model.
- Pro — Community plus Patrol investigation, governed fixes, ninety days of history, centralized agent profiles, RBAC, audit logging, and reporting.
- MSP — for managed service providers: one Pulse Account running many client workspaces, each with an isolated Pulse runtime — separate dashboards, alerts, users, audit history, and reports. Free sixty-day two-client evaluation at Pulse for MSPs.
Relay is no longer sold. Existing Relay subscribers receive Pro features at their current price for as long as their subscription continues. Existing paired phones keep working until 31 March 2027. Relay connects the app, not the web UI. Use your own VPN or tunnel for remote web access. For phone alerts, add an ntfy, Gotify or Pushover destination and open Pulse in your phone's browser.
Core self-hosted monitoring is not gated by monitored-system or child-resource volume. See the runtime-aligned capability reference and current plans for details.
Documentation
- Install and deployment
- Production deployment and security
- Upgrade from Pulse v5
- Releases and update channels
- Configuration
- Platform and agent guides
- Pulse Intelligence
- Security and privacy
- Code signing policy
- Troubleshooting
- API reference and architecture
Localized getting started guides: Deutsch · Español
Development
Pulse uses Go 1.26 and a SolidJS/TypeScript frontend. The managed development
runtime starts the frontend at http://127.0.0.1:5173 and proxies API and
WebSocket traffic to the backend on port 7655.
npm ci
npm --prefix frontend-modern ci
npm run dev
Useful checks:
go test ./...
npm --prefix frontend-modern test
npm --prefix frontend-modern run type-check
python3 scripts/check_public_docs.py
See CONTRIBUTING.md before investing in a code change. Pulse uses an issue-first contribution process and does not normally accept unsolicited pull requests.
Community and support
- Ask questions in GitHub Discussions.
- Report bugs and unexpected outcomes through GitHub Issues.
- Home Assistant users can use the community-maintained Pulse add-ons.
- If Pulse is useful to you, support its development through GitHub Sponsors or Ko-fi.
Read the safe reporting guidance before sharing original evidence. A second reproduction or diagnostics export is not required; do not repeat an attempt that could interrupt workloads or send duplicate notifications. GitHub reports and attachments are public: review them locally and keep credentials and private details out.
License
Everything in this repository is licensed under the MIT License. There is no dual licensing and no commercial or source-available code here.
Pulse Pro is a separate commercial product, built from private sources and distributed through pulserelay.pro. Its use is governed by the Terms of Service, which apply to that product only, not to anything in this repository.