pulse-triage[bot]
a7a4a9aa41
## What changed and why This batch repairs existing setup, administration and History surfaces: - PBS and agent guides keep tokens out of shell history and process arguments, prefer read-only identities, and require verified HTTPS downloads saved for inspection. Fleet/action, RBAC, audit and organisation examples use private header files, supported schemas, signed-in session-only mutations, custom-role operations and private exports. - Generated Proxmox setup separates credential reveal from copied commands and uses private-file handoffs. Download/preflight, permission, identity and cleanup boundaries remain intact. - Shared tables regain first-touch activation without swallowing embedded controls or keyboard disclosure. Sparse drawer History displays real stored observations without inventing trends, labels current fallbacks honestly, and explains empty windows. - Demo chart series reuse graph-version-bound metric samplers rather than rebuilding the whole estate for every series, preserving values and isolation. - Release-note validation accepts authored grouped notes while retaining identity and safety checks; qualification binds the complete current source rather than an incomplete filesystem list. These are repairs to existing behaviour and unsafe or inaccurate guidance, not new features or permissions. PBS source/browser improvements do not establish complete installed resolution of the mixed #1723 report. ## Included source Complete unpublished `pulse` range `e5082c5fb1be8f8882275338d8b9f088b6a41cc4..f047d7b5db78ef1e3ca0b84de4fe2f6c43a9311c`. This extends the former PR #2362 head `704f4eeb4ef4f29cb0341d847665516b315cc24a`, whose workflows have completed, rather than restarting an actively checking proposal. Reviewed candidates and their additive integrations: - PBS guidance `a5c8b5d59799c7cf43af0f0fc7e796722c95fe7f`, integrated at `6a47dad9ce60a3814ad08de0814dff84493b5453`. - Touch-row candidate `88f52387af1fe6ebd6554acd49320a2e5927c0e8` and lint correction `12c8a7aba39bd8457f541ca0b1cc045893aed5db`, integrated at `36418af66beac94204276f7dc73de2c41e297fb1`. - Agent guidance `d5c187613a68e6e891ae9a5b6dbfd6154cea1844`, integrated at `9bbbc7a817274ab13b9c20b2119f46edd94d2109`; fleet/action guidance `704f4eeb4ef4f29cb0341d847665516b315cc24a`. - Sparse History candidate `b405f8d99b252bfc0e8773914fe07c96e2ab7f59`, retaining runtime `ec372845541fd0a79800b9ccadd7f4972be5e836`, integrated at `a5347278430342fd805e758897c00ce187579d66`. - Release-note/qualification candidate `90c80acb493eb4ff6a789b184a794b87b4a6d538`, integrated at `22380a35460a255ac4d60e20549e959875ccbc21`. - Private-bootstrap/demo sampler candidate `cf12c37e6302883e66039078d6e504b1014b26cc`, integrated at `0832be112f024f5a6dd695da42b134e9039c2840`. - Administration guidance `0c3cd4fb3ad1a32cb7ddb00b0992a53991594b79` (three own commits), integrated at `7d5c6eb0045f94481ae3147476187e9ad2eeccda`. - Additive corrections `0fd47f7ebf5da8588d62b9f81b336b5267e3430d` and `5116c2a2d9e49e83e794d23cf99e40c240e51ad9` reconcile the PBS guard and explicit TLS fixture floor with accepted safe guidance and current release direction. - Upstream merges `f5e305d4c9494830743a140bbb1f951694555c38` and `f047d7b5db78ef1e3ca0b84de4fe2f6c43a9311c` retain published ancestry, including upstream's independent shadow lifecycle rehearsal. No accepted identity was rewritten. ## Validation and adverse evidence Sufficient existing candidate evidence is reused, with fresh bounded reconciliation checks: - PBS `source-1bj5m4w1`: 28 checks; frontend documentation/build/budgets `source-dz1jcq79`. Fleet/action `source-cb0mkbhb`: nine executable guide tests; frontend `source-qynvs3_n`, 32 browser checks/four inspected screenshots. Agent guidance has six executable fixture tests, including private-file permissions and filename-only handoffs. - Touch candidate: four WebKit/Chromium/Firefox phone/desktop cases, embedded-control and keyboard assertions, 12 inspected screenshots. Sparse History final `source-nha4kbvo`: formatting and 121 affected tests; predecessor full type/lint/test/build/budget proof and four browser passes/32 inspected screenshots. Parallel `source-_d931osk` failed one existing window-test timeout; that result remains adverse, not an overall pass. - Bootstrap/demo `source-rlyqg2wg`: full affected configapi/hostagent/mock/monitoring/installtests race suites and affected API cases; `source-p2vo7bpw`: affected vet and actual frontend/server/agent builds. `source-l681cvrh` records frontend type-check and 21,612 tests; browser matrix covers PVE/PBS desktop and emulated phones with eight inspected screenshots. Earlier full API timeout and output-limit attempts remain unresolved, not passing receipts. - Release-note closure `source-ig3ted7j`: complete install suite and 942 Python cases/eight skips on its recorded source. Final fixture correction `source-in4fqcsx` passes authored-note tests and seven negative safety/identity subcases. - Administration `source-_klnz0rf`: 55 documentation tests, 26 API tests, authentication tests and documentation audits. Frontend `source-lrr0gmox`: 50 documentation tests/build/budgets; 41 browser checks/eight inspected images. Fresh full-range provenance and whitespace pass. All 23 unpublished non-merge commits pass the prescribed per-commit completion/browser checks using their recorded Contract-Neutral reasons where applicable; aggregate browser coverage binds all six changed frontend runtime paths. All 62 shipped-doc mirrors and 211 public Markdown checks pass. A naive aggregate shape check fails because it cannot honour those per-commit reasons; the workflow-prescribed per-commit check passes. The repaired PBS required/forbidden source assertions were separately checked against the final text. An optional additional source-VM check was cancelled while queued, before execution: no receipt or pass is claimed. Former-head CI runs `36829661316` and `36829661309` failed the retired credential-bearing PBS assertion; the accepted additive corrections replace it. The former CodeQL finding concerned the local TLS fixture's implicit protocol floor, now explicit. Former advisory benchmark `ConcurrentReadWrite-4` remains failed: 906.4→1007.7 µs, +11.17%, p=.011, n=10. Its former candidate and base have identical Go sources/manifests, but this does not prove the cause or turn the measurement green. The observation is retained for independent Delivery assessment; fresh exact-head CI remains necessary for the expanded batch. Required exact-head checks and independent review govern landing. These are synthetic/source proofs, not physical-device acceptance, native installation/recovery, complete PBS reporter acceptance, deployed activation, release qualification or availability in a release. [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.