pulse-triage[bot]
b433165658
## Additional repair in this publication Restore native TrueNAS CORE monitoring for #2077 across CPU, memory, measured temperature, device-bound network/disk I/O, and History. Native RRD rows use external timing and legends rather than embedded timestamps; empty/null buckets remain distinct from measured zero. CPU states are normalized, ARC stays aligned with free RAM, stale readings are not presented as current, graph selection/splitting is bounded, and absent device graphs cannot produce misleading partial host totals. Measured temperature also reaches the existing local and persistent Thermals paths. The complete publication range is now `4317db177e341a0ca52b649c258ac43bc0135d0b..b32a4369e7f55c39a4baed0f122336384185618d`. It preserves every commit in the preceding proposal and adds native CORE candidate commits `b50313c59998d0e1506ab5ca42730bbb2e386dcd`, `c78840e3717b7dd3794ed401529e5f4bdcab2e50`, `bab5cf77d60f5252311bad05f28aecb4d76f1de1`, `579eee290759f5518f6ef16d0b9189a2dec7d856`, and `45eec9a20eac55a356acfb1c17833cd6c8d067ad`, integrated by `b32a4369e7f55c39a4baed0f122336384185618d`. The previous head completed its checks. Governance run `36949586647` failed the remaining subsystem-lookup list assertion, while its reported build/test, frontend, eight E2E shards/verdict, boundary, docs, security and benchmark checks succeeded. Additive `50c24260cab18db1609be0bb1ea91d89c6c99f70` aligns that assertion with the existing startup verification, without removing coverage. Because a corrected head is necessary, the independently reviewed CORE repair is included now; this does not interrupt a still-checking head. Recorded CORE validation: `source-7of9at5x` passes full TrueNAS correctness/races/vet and connected monitoring controls; every TrueNAS blob is unchanged here. `source-6mf6bu65` reproduces the predetermined parent thermal-write fault and passes final connected/writer correctness/races/vet, including local/persistent History and the local-window fast path. `source-d3jaf8_z` passes real embedded frontend and server/agent builds using verified matching dependency inputs. The integrated CORE/monitoring/registry source exactly matches that proved candidate. Earlier ARC/cancellation failures were corrected, not dismissed. `source-woncpjdu` remains overall failed after 44 frontend cases/typecheck/assets passed, because it selected the wrong module's Go cache; it is not a full pass. Native appliance/browser/containing-stable acceptance remains separate, with compatible next-patch placement owned rather than adding this work to the frozen v6.4.6 quartet. Publication provenance passes; both available upstream tips match the inventory and are retained ancestors. Current-workspace registry/contract and per-commit completion guards pass. The gate's confined native-Git executor passes all 163 subsystem lookup fixtures, including the previously failed assertion. Earlier proposal evidence remains applicable to its unchanged scope, as retained here: ## What changed and why Queued alert notifications recheck the current quiet-hours schedule when they become due, including continuous schedules and late replay. Held items do not consume a provider attempt; mixed batches deliver only eligible alerts, preserving destinations, retry budgets, acknowledgements, cancellation and recovery. Startup binds saved policy before persisted work starts. Schedule edits do not accelerate already-future deadlines. Agent troubleshooting distinguishes permission from an admitted, connected command channel, addressing the confusion in discussion #2333. Notification troubleshooting distinguishes a direct test from real alert delivery, explains retained-failure recovery and duplicate-retry risks, and replaces an unbounded email pipe that masked reader failures with bounded local readers. Both Docker streams and exit status matter; raw provider bodies may expose private information. Source guides and shipped mirrors agree. ## Complete range and proposal repair Published main base `4317db177e341a0ca52b649c258ac43bc0135d0b` through proposal tip `57cd5171c234c5f9626625e2bc0b237de6b4c277`: - Quiet-hours runtime/tests/contracts `5213b794b2856fe260ccb3fade0af29efddeda44`, registry-order correction `c3f627d0d68811cbcc0d7466e0376e83679a0658`, integration `defaa2344de20d51a681f76b9cf7a57fd215ba7d`. - Agent-channel guide `c08583dd54a8462566ad34094fcc7e8f577bf854`, integration `fc4deb6c177183a06f201794a4fd90735ab9fd06`. - Notification guide/tests `76e1aea061bb60d0922e27fb799a79198bd8de07`. - Additive governance fixture corrections `96986379d1d88d81ea56dc872ba3183b11e35419` and `57cd5171c234c5f9626625e2bc0b237de6b4c277`. The preceding proposal finished CI: governance run `36940673378` failed two fixture expectations after the reviewed startup test was added to the verification registry. The correction aligns all three affected exact-list expectations, without changing policy, coverage or runtime. Every previously reviewed identity and author is unchanged. All sixteen files in the earlier proposal still match it exactly. The newer independent guide is included now because a corrective proposal head is needed, not merely to restart an already-running batch. ## Validation - Recorded `source-5mneylzw` reproduced predetermined predecessor faults and passed final affected alerts/notifications correctness/races, bootstrap races, vet and package builds. `source-fmtyrqhz` passed final-tip equivalence and focused replay/startup races. - Recorded agent-guide controls and thirteen recipe tests passed in `source-5y8u5a2z`; `source-059hcqfl` passed 25 documentation/mirror cases. These are not native appliance recovery. - This gate's confined native-Git fixture executor passed all 132 governance fixture tests and all 38 notification/request-log/mirror/agent-troubleshooting cases. The first partial governance correction still failed the later monitoring assertion; that failed attempt is retained, followed by the complete correction and pass. - Public-doc checker passed for 211 Markdown files. Publication provenance, whitespace, each source commit's completion guard, registry audit and contract audit passed. Browser guard explicitly skipped: no user-visible frontend source changed. - Earlier `source-t_33yywy` had 97 passes and an unchanged agent-profile timeout; later omitted-check clients did not execute during gateway restart. Relevant changed-guide checks are now complete; the unrelated token-profile timeout and frontend-only self-chosen proof remain separate follow-through, not full-suite passes. - Optional `source-44iq3ddd` whole-profile VM audit remains failed on unavailable repository identity/wider layout. Actual-workspace audits pass, but do not change that receipt. Recorded Go proofs used 1.26.7, not the declared 1.26.8 environment; no full application build is claimed. Exact-head CI must pass before landing. Natural schedule/day/DST, destination/recipient and installed command-channel acceptance remain separate. This neither changes the frozen v6.4.6 quartet nor approves any release; compatible quiet-hours next-patch placement stays owned separately. [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}"
rm -f install.sh install.sh.sshsig
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.
- Relay — Community plus secure remote web access, Pulse Mobile pairing, push notifications, and fourteen days of history.
- Pro — Relay 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.
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.