pulse-triage[bot]
24723dd642
## What changed and why - Guest filesystem History distinguishes paused/retained readings from current observations. Incomplete readings stay unavailable rather than appearing as healthy empty disks; measured zero and known capacity remain useful. Related to #2439 and #1723. - Installation help removes the minimal root-server service recipe, explains the existing hardened installer and distinguishes a missing unit from a loaded root service. Removal guidance preserves persistent data by default, explains temporary container storage and Helm claim ownership, requires a consistent private full-state backup and separates disabling the service from destructive erasure. - TrueNAS setup help distinguishes a successful system-information connection test from collected inventory/metrics and preserves polling evidence. Passive VM preflight rejects malformed configuration before concluding that an agent setting or backup lock is absent. Related to #2382 and #2439. - The native backup evidence checker requires observed post-task filesystem and memory reads, not merely fresh-looking timestamps. - Add an exact-published-RC browser update/recovery workflow with authenticated archives, reviewed control identity, a dedicated narrow CI registration, self-only Serve and terminal refusal handling. It is a qualification route, not a qualification result. The documentation and filesystem changes address unsafe implications in existing surfaces; no new product route or feature is added. The browser route supports the required release update/recovery journey. ## Included source Range: `13df84e9038be8017110105186b44f626154a3f6..c0ceff669774cec9f3b71f0bade244133f9949bb`. All previously reviewed identities and their ancestry are retained: - TrueNAS candidates `1c999113` / `59a27e2c`, integration `22f16541`, additive published-main merge `a6b83db5`, passive preflight `adcd0ddf` (the original PR head). - Installation candidates `a6959e57` / `01adf338`, integration `6cf691ec`; data-preserving removal candidate `fa6282b7`, integration `0f3575bd`. - Filesystem/History candidates `28bb0fb5` / `81b07e8a`, compositions `ba8b9fcd` / `5d1b03c1`, integration `53cfdf60`. - Browser-route candidate sequence `fdf46457`, `619133aa`, `729b2cf7`, `f0ff1934`, `73b790b8`, `d855d322`, `30ca9681`, `a847b05e`, `2fb4bf9e`, integration `b42563d9`. - Backup-resumption checker `1920db3c`, integration `acace4d4`. - New additive publication correction `c0ceff66` normalizes only Markdown whitespace and capitalization in the TrueNAS safety assertions. Every required warning and diagnostic field remains checked; documentation/runtime content is unchanged by this correction. ## Validation and remaining limits Recorded reviewed source evidence includes full TypeScript checking, 407 filesystem/UI regressions across fifteen relevant families, production embedded build and unchanged bundle budgets (`source-bnh7z6xi`); 58 removal-help controls/types/build/budgets (`source-f_l3trzu`); inspected desktop Chromium and phone-emulated WebKit help and filesystem states; 57 connected browser-route controls/workflow trust (`source-agx1sbr6`); and nineteen focused backup-checker methods. These remain evidence at their original source bindings. Publication comparisons confirm unchanged validated runtime, removal guidance and qualification-route bytes; the final browser guard covers all four changed frontend runtime files with their in-range receipts. Exact final-source offline smoke receipt `source-ljvxb1yx` at `c0ceff669774cec9f3b71f0bade244133f9949bb` ran 59 families: 57 passed, two failed; exit 1 with complete output and confirmed guest stop. All changed smoke families, including the corrected seven TrueNAS tests and new browser-route controls, passed. The failures concern unchanged historical Git fingerprints (unavailable objects in the disposable source input) and an extra synthetic npm-audit invocation. The same unchanged tests passed in the original hosted PR run and all 21 pass in a confined lightweight native-Git comparison. The npm observation remains unresolved with Delivery; the complete VM suite is **not** reported as a pass or replaced by the comparison. Publication also verifies provenance, clean committed source, upstream and starting-reviewed-tip ancestry, matching documentation mirrors and whitespace. Removing either affected safety warning still fails the corrected assertion. Sufficient completed frontend/browser proofs were not repeated just because their changes share this batch. The original PR's completed run `37175962472` failed required script smoke on capitalization/line wrapping, now corrected additively. Its advisory benchmark reported `HandleMetricsHistory_MemoryFallback/all-metrics` +12.58% (p=0.019, ten samples). No Go or benchmark source differs between that original head and its base; this is not a causal diagnosis or a passing measurement. The adverse result remains with Delivery for independent disposition. The old head has finished checks and cannot land independently because of the required smoke failure, so this proposal advances once to include the coherent reviewed batch and correction, rather than restarting still-running CI. Exact-head review and protected checks remain required. Earlier unexecuted readiness attempts are not reconstructed passes. This source does not establish native thaw, TrueNAS collection, installed recovery, a containing release or deployment. The browser route still needs its dedicated registration/ACL prerequisite and activated dispatcher before native use; the earlier HTTP401 remains adverse and unreplayed. Release qualification, soak and promotion remain separate. [How Pulse handles triage](https://github.com/rcourtman/Pulse/blob/main/docs/AI_TRANSPARENCY.md) ## Additive follow-on batch and final publication check The completed exact-head Build and Test run `37179468966` cannot land: its required rest-1 job rejects the browser workflow's Node `24.20.0` selector under the existing governed `24` parity contract. Correction `903dc08d23d4278103950e0df6ed5f7b8fb97760` selects the same `24` line as other workflows and adds a focused trust regression; no parity assertion, pinned action, browser tooling, privilege or release gate is weakened. The old head is terminal, not still validating, so the proposal advances once with this repair and the coherent reviewed follow-on source. Final range: `13df84e9038be8017110105186b44f626154a3f6..903dc08d23d4278103950e0df6ed5f7b8fb97760`. Additional accepted identities, preserved unchanged: - Complete VM-configuration response boundary `227f4f7e` / composition `f7eeabc4`, integrated by `de081296`: do not admit guest reads from an incomplete unlocked JSON prefix. Related to #2439. - Token help `74c35227` / `383be305`, integration `630f45a2`: match seven least-privilege presets, distinguish prompt exposed-token revocation from planned rotation, and explain kiosk bearer-link and per-tab limits. - Guest workload evidence `23235502`, integration `0e41d8d2`: preserve existing disk-deferral, guest-agent and lock facts through API and canonical snapshots, clear obsolete omitted facts only after an explicit new native outcome, and withdraw unavailable numeric bars while preserving labelled prior and measured-zero readings. Related to #2439 and #1723. - Used-memory History retention `0ea87307`, integration `768952fd`: expire byte samples alongside existing series without deleting still-live byte-only resource entries. This is not an attribution of reported process memory growth. Aggregate reviewed evidence adds `source-hctbddnb` for complete-response parent/final race controls; `source-n8_u1xm9` for 37 token-help controls, types/build/budgets, with fixture-only syntax `source-5ws674f3` and six inspected desktop/phone-emulated captures; `source-c8k64dn9` for types, 761 tests in eighteen relevant files, lint/audits/build/budgets, forty browser transitions and six inspected captures; and `source-0qcd2wj7` for adverse parent omissions, final retention and connected History readers under race/vet/affected-package build. These retain their original source bindings. Publication comparisons confirm final changed Web runtime and Core Go bytes match those tested candidates, and the final browser guard covers all seven changed frontend runtime files through their own-parent in-range receipts. Sufficient compiler, build and visual proofs were not repeated solely for batching. Exact final-source offline receipt **`source-1_rh272s`** at `903dc08d23d4278103950e0df6ed5f7b8fb97760` passes the previously failing Node parity test under race, selected guest-agent/backup/History/memory/metric-window families in Proxmox and monitoring under race, 18 browser-packet/Tailnet controls and 43 workflow-trust controls. Exit 0, complete 11,065-byte output and completed guest stop; this is focused source proof, not a full-suite or release qualification claim. The same old-head run also reports advisory `ReportMarshal_Parallel-4` +23.25% (p=0.009, ten samples, candidate spread 19%). At that old proposal head, Go/dependency/build-and-test/benchmark source is unchanged from its base. This establishes no changed benchmark source, not a passing measurement or a cause. It remains adverse alongside the earlier +12.58% History result under the existing Delivery disposition request. No unchanged retry, threshold relaxation or release clearance is claimed. The newer retention repair changes Go source, so it is not covered by that unchanged-source comparison. New exact-head required checks and independent review must finish before landing. [How Pulse handles triage](https://github.com/rcourtman/Pulse/blob/main/docs/AI_TRANSPARENCY.md)
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 nothing runs on the host and 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.
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 reproducible bugs 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.
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.