pulse-triage[bot]
1d4c3aeb6e
## What changes and why Keep guest monitoring truthful while reads are deferred: retained memory/filesystem values must not become new alert decisions, new History observations, current filesystem health, or continuous chart lines across missing readings. Failed or empty metadata refreshes retain the last useful observation time rather than manufacturing freshness. Independent current readings and measured-zero recovery keep their existing behaviour. Manual guest Discovery pauses during the existing backup/read precaution, preserves saved evidence, and keeps delayed outcomes attached to their original guest and run. The published drawer-header link to a saved web interface remains available separately from live Discovery. The existing TrueNAS guide and shipped copy keep credentials and responses private and bound individual requests. The guest work follows the prolonged freeze reported in #2439 and reproduced downstream observation/lifecycle gaps. It does not identify the freeze's cause or prove native recovery. The guidance repair follows inspection of unsafe existing recipes. No new collector, schema, retention policy, threshold or product surface is introduced by this batch. ## Included source and reconciliation Current published base `efe6fc21ae10a6bf173cc17e6203aaf6c97dc130` → proposed head `1914f5fb7b278b5fc4cc10a292e909a10714a2f8` (39 introduced commits, including additive integrations). - TrueNAS guidance: `cadfd1f4e1d9f909a45977f94aadd4f1324e82ef` → `d589407a743a12fe492e93785d9e24c12bbb4fb5`. - Discovery pause/outcome ownership: `2cb3f6a9043e0bab9c54c5b5ef57b3e1cb994781` → `bbaee0a3f43dc7906011be5c78d684f9a1327bae`, including additive recovery and lifecycle controls. - Alert admission: `b0f8b96c8a159ac242b85f2d09f8dfffd5c29c7a` → `0fd7768e9d1379f8aa0126b33d4047b4c52c0d87`. - History writer admission: `a15920eaebea00ab8c353ddd3861b9cd7ff7d379`. - Filesystem presentation: `2525d76c04a9834c2130e97c1a529e164a9c7796` → `5b75f21159fda3c01fbe6688aa9cfde68779fba8`. - Metadata freshness: `f1e221a0fb9b0804f200c13490f8526424cb7e1c`. - Missing-observation chart presentation: `0ad41e4c9a309ce459dd717d16d343b46efcac8a` → `5e7e49650fcdf5131b7c5006fe487336ab660e15`. - Platform-aware Discovery fixture: `a2608c9fadf76c242527a636ee08968fa16ddde8`; TrueNAS recipe reconciliation `1f0d12af85ec7c2ad8df391b8e6958e80fa98179`; additive upstream/header composition and content-bound browser receipts through `b01dad904c3436e70bc01588ea1546fffaa05dc6`; batch-start upstream merge `f1c7e413bac2e3306d2169bcd069c60325e56d5f`, then exact bounded refreshed-upstream merges `07112b0e3ab2be174a5ac7a11f87ac0837edceb0` and `1914f5fb7b278b5fc4cc10a292e909a10714a2f8`. The previous proposal head `6a20d106242598bd6b466e9ae888ea931d284b30` is completed-failed, not still validating. Native run `37239183481` incorrectly required a Linux/PVE capability on Windows/macOS; Build and Test `37239183545` extracted zero wrapped TrueNAS recipes. Reviewed additive fixtures correct both without weakening runtime safety. The old head cannot land independently, so this update includes those corrections and the coherent observation batch. Every accepted commit identity and all ancestry are retained. Published cluster labels, saved guest links, unique demo workload names the newer storage priority/alert explanations, and the published Alerts overview are preserved. Bounded refresh receipt `2916978f4e4b49d084752e973e19a5c0f7dd19f0bf4ac60cc31875876318528d` completed at the exact observed upstream without changing source; the subsequent full-SHA merge composes it additively. A second successful bounded refresh `59f1939979347921d99e262398d5347077bfce6faf6f42535050840a3a19820b` incorporates the subsequently published Alerts overview in the same way. Neither is a replay of a failed or uncertain attempt. ## Validation and remaining gates Retained evidence includes connected alert/API/producer/recovery controls (`source-p58_phvc`), Discovery/component/build/browser checks (`source-gy5x8buj`), installer/docs controls (`source-7s0iorys`, `source-uo6rxs61`), metadata connected/race/vet/build proof (`source-ji23nb_c`), and ten connected suites plus focused safety races/vet and native-target compilation (`source-seboen4h`). Browser content receipts cover the final seven changed frontend runtime files, including the composed saved-link/safety header and chart gaps. The History presentation proof `source-ualisb1k` completed 22,571 frontend tests across 1,234 files, types/lint/format/build and bundle/integrity checks; its overall exit 1 from trailing nonexistent optional test paths remains recorded, not converted into a whole-command pass. Four browser groups/32 checks and eight inspected captures separately passed. Earlier reproductions, fixture failures and reporting-limit failures remain evidence. Publication-gate checks: - `source-qt6m6mf_`: seven connected TrueNAS recipe controls, full mock suite, scoped real agent/guest safety, alert observation and metadata/History tests pass. Backend/docs source is byte-identical in the final composition; this evidence was not repeated after frontend-only upstream advances. - `source-xy1lnmgt`: types pass and 281 of 283 scoped frontend controls pass; two first-case History tests hit the unchanged 5,000ms timeout. Exit 1 is retained and the following build did not run. No functional assertion failure or cause was established. - One predeclared single-worker/file-serial comparison, `source-17bch24o`, passes all 23 controls in those two files with unchanged source, assertions and timeouts. This establishes isolated functional behaviour, not a diagnosis or clearance of parallel CI. - `source-dvlfnm5t`: refreshed storage composition passes types, 1,177 tests/56 files and the real production/embed build. The event-parser line-bound flag is recorded; the complete 26,474 raw bytes independently match the receipt. - Final exact-head `source-sjjtzjqm`: types, scoped published Alerts overview/translation/presentation controls and the real production/embed build pass. Complete raw output is independently hash-matched and the guest stopped. - All executed receipts, including the failed scoped run, retain complete output and completed guest stop. Provenance, clean source, diff/ancestry checks, all 24 introduced non-merge commits' parent-bound canonical guards using only their original recorded trailers, and the final seven-file browser-content receipt guard pass. Required exact-head administrative source review and GitHub checks must complete before landing; this update is not a blind failed-job retry or a CI waiver. Native overlap, independent thaw, fresh writes on every covered filesystem, workload liveness, truthful alert delivery and safe restoration of only prior-active services/timers remain separate. UI clearance, saved values, an OK backup or these source tests are not recovery, a containing release or installed/reporter acceptance. Related to #2439 [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.