pulse-triage[bot]
0e90236d3b
## What changes and why - Storage History readings can be inspected by touch without a later compatibility-focus event replacing the selected sample. Scrolling, gesture cancellation, keyboard inspection and measured zero readings are preserved. - Storage pool details use the owning host's physical disks, temperatures, SMART facts and topology counts. Repeated device paths and UnRAID group names no longer mix facts from different hosts; unknown ownership does not invent membership. - TrueNAS skips app-stat subscriptions for empty app inventories, disposes of failed retried streams, and preserves successful retried log-tail completion. Session-close diagnostics use classified local causes rather than private wire data. This repairs the empty-inventory path reported in #2396. A later reviewed repair now handles matching subscription-termination notifications without stalled acknowledgement or stream reads. The association is source-derived, without a retained native capture; #2400's reported 60-second close remains unexplained. PBS History guidance also now recognises the drawer's batched `metrics` response rather than asking readers to find a separate CPU request that the drawer does not send. This follows the empty-batch response supplied in #1723 and preserves privacy-safe diagnostics. These are repairs to existing monitoring and inspection surfaces, not new collectors or features. The storage defects were reproduced in the existing desktop/phone presentation. ## Included source Complete unpublished range: `f26182f98ccd0e9ee1089bf651d41e0003871ed2..90c436c83d616eccbe544bf3737b13c3b6251e53`. Reviewed candidates: - `7c48430d5a3ed0eefc677b6a5ccc50ee4bc0920a` — History touch inspection. - `34f73590bbb72c01a3e16e6085227849556a2b1d` — pool disk ownership. - `b8cc3b44f8b7e1bd927b0368b10d59f37ede2187` — TrueNAS empty-app/stream lifecycle. - `7b370c7db9941bba4037a888230cb513c02927c0` — PBS batch-aware diagnostic guidance. - `f0ea29480e172631e71ed8da54de95e9cfabda22` — exact subscription termination and polling recovery. Integration merges preserve their original identities and incorporate the published mock-replication, Kubernetes job-time, audit and release-source-mapping frontiers. Additive merge `90c436c83d616eccbe544bf3737b13c3b6251e53` incorporates current main's Patrol weekly-summary scheduling (#2423). The conflict was limited to appending both frontend contracts and retaining the unchanged upstream receipt pointer; runtime source is byte-identical to the respective verified candidates. No accepted commit was rewritten. ## Validation - Retained storage candidate proof: 21,743 tests passed, three skipped; typecheck, lint, production/embedded builds and budgets passed, with complete output and guest shutdown. - Retained Chromium/WebKit parent/final controls cover touch inspection and 12 pool-ownership presentation states, including mounted host replacement and isolated History requests. - Retained TrueNAS proofs cover correctness, races, vet, five focused race repeats, connected monitoring/API checks, backend compilation and 132 completion-guard tests. Initial missing-object setup and a later governance-import exit 1 remain adverse evidence; corrected discovery passed separately. - Retained PBS guide proof `source-h1cvqpr3`: eleven tests and inspected production Docs in desktop Chromium and phone WebKit. - Retained termination-repair evidence: full TrueNAS correctness/races, five focused race repeats, connected three-poll recovery, persisted exact PBS batches and identity controls, vet, server/agent builds and 132 governance tests. Eight completed attempts retain three adverse fixture exits; their corrected controls are separate results. - Publication composition: browser range guard confirms all seven changed frontend runtime files across the original common-base range match in-range receipts; completion guard passes on the composed published-base range without overrides. Tested runtime blobs remain identical, provenance checks and diff whitespace checks pass, and both remote/main ancestry and a clean checkout were verified. A redundant confined-host guide check failed to open localhost sockets (eight errors); this is an execution-context failure, not a passing check. The unchanged guide retains its successful disposable-VM proof. Limits: local Go proof used 1.26.7 rather than declared 1.26.8, and backend compilation used an embed fixture. Exact-head CI remains required. Synthetic presentation and source proofs do not establish native appliance acceptance, whole-report resolution, release availability or promotion readiness. This does not alter the frozen published v6.4.6 RC. [How Pulse handles triage](https://github.com/rcourtman/Pulse/blob/main/docs/AI_TRANSPARENCY.md) [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.