pulse-triage[bot]
834fcaeb36
## Outcome This batch makes guest identity persistence safer, keeps broadcast resource rows and their History targets in one captured generation, and makes completed-backup evidence accessible by keyboard and touch. Existing help now explains container CPU scales and passive comparisons. Native macOS guidance checks receive real GNU timeout without replacing unrelated system utilities. The work follows retained identity-write/shutdown failures, fleet CPU and History consistency evidence, inaccessible backup disclosures and confusion about container CPU readings. It improves those existing paths without claiming field recovery or complete performance relief. ## Included reviewed candidates The complete proposed range is `800329cbd83c48fdb7402a18633189f2c8a2d6ff..9b057cb141221526a96fac05bdbdf8ed6e8625fc`: - Guest metadata ordering/coalescing and safe retained shutdown: `244d322dce` and `5e51069048`, integrated at `d7a305922a`. - Native guidance prerequisites: `13f6d10798` and `443faa53b6`, integrated at `f7fca0e164`. - Accessible existing Workloads backup details: `02e6a90374`, integrated at `8661c1fc65`. - Paired complete resource/History capture and faithful full-content controls: `54de7bdca7`, `32f09dc13d`, `8b12e0ee1b`, `d206b03990` and `9cc8523881`, integrated at `2787b4eabd`. - Container CPU documentation: `0c283d2dd5`, integrated at `15e8c5ccf6`. - Router-owned limiter joins and sealed late worker admission: `5b560521e2`. Reviewed identities and authors are unchanged. Current upstream Docker link editing and platform layout repairs are incorporated by an additive full-SHA merge; earlier upstream governance and Kubernetes layout history are retained. The later upstream Docker image badge sizing repair at `800329cbd83c48fdb7402a18633189f2c8a2d6ff` is also retained after one successful bounded refresh and additive merge. ## Behaviour and safeguards Identity polls merge only monitor-owned fields, preserve operator links/tags/notes and OCI classification, and do not spin-retry filesystem failures. Incomplete tenant shutdown retains ownership and prevents directory removal. Router shutdown joins its own limiters without resetting budgets or stopping another Router. Broadcast resources and target mappings are detached together. Health comparison controls use one evaluation instant while production still samples real UTC at the existing boundary. Full-content, overlay/clear, identity and observation-time controls remain. Backup disclosures preserve hover and add keyboard/touch access to the same read-only evidence. CPU guidance distinguishes host-capacity normalisation, VM CPU counts, version-qualified rounding, missing readings and actual alert delivery; it asks for ordinary observations, not forced workload or threshold changes. ## Validation and remaining limits - Provenance, retained ancestry, clean additive merge and whitespace checks pass. - Every unpublished non-merge commit passes the canonical completion/history guard. Final-range browser receipt coverage, public registry audit and contract audit pass. - Accepted candidate evidence includes focused writer/API races, startup observations, vet and actual builds; 363 connected backup frontend tests with four desktop/touch browser cases; CPU help's 132 connected frontend tests, lint/types/build/budgets, focused Go checks and four Docs browser cases. Browser receipts cover unchanged final backup bytes and are not rerun merely because the batch contains several candidates. - Gate frontend proof at `9daeed13`: 246 tests in four connected files, type-check, all lint checks, actual embed build and bundle budgets pass; complete output hash matches and guest stop completes. - Exact refreshed head `9b057cb1` passes 49 Docker native-table and platform-layout guardrail tests (`source-l8diazgn`); complete output and guest stop are verified. This covers the later width-only upstream change without repeating the earlier full frontend checks. - Gate backend attempt `source-pz6qwk2t` fails in guest readiness after capacity waiting, client exit 2, with no command verdict and confirmed guest stop. It is not a test pass and is not replayed. All backend Go source, manifests and native workflow bytes are unchanged from reviewed `5b560521` and its focused races/vet/real-build evidence; that evidence remains usable without inventing an aggregate pass. - The retained broad API ten-minute timeout, earlier drain/startup failures, adverse allocation/frame costs and failed stable RSS retest are not erased by these focused results. Required exact-head CI remains authoritative for landing. - This is not native guest thaw/recovery, PBS badge agreement, CPU/RSS relief, notification delivery or release inclusion. Independent thaw, fresh writes on every covered filesystem, liveness and only-prior-active restoration remain necessary before resuming uncertain monitoring. Related to #2199 Related to #1723 Related to #2439 Related to #2447 [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.