mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-27 14:07:31 +00:00
rcourtman
5996dc1a25
The Proxmox guest and node drawers' Overview was a grid of equal-weight inventory cards, much of it repeating the table row, while the trend that answers "is this getting worse?" sat on the History tab. **Overview now leads with what is wrong:** - Active alerts first (unchanged component), or one "No active alerts" line. - 24h trend cards for the metrics the row shows: CPU, memory and disk for guests; CPU, memory, CPU temperature and root disk for nodes. A card with an active alert on its metric is coloured and draws the alert's own trigger. - "Worth checking": any warning- or danger-toned detail row, lifted from whichever section owns it, so demotion never hides a reason a reading cannot be trusted. - Guest filesystems, physical disks, RAID, node GPU/NVMe sensors, and any availability check that is not both fresh and healthy stay visible. - A one-line facts strip (OS, address, healthy last completed backup, tags). - Everything else in a closed **Details** disclosure that keeps its rows mounted for find-in-page. **Correctness details:** - Trend cards and the History tab share one query and cache key (`guestDrawerHistoryQuery.ts`); each polls only while its tab shows. The node drawer's History no longer stays mounted and polling while hidden. - Node cards are coloured only by the node's own alerts, which `ProxmoxNodesTable` now passes as `ownAlerts` by identity; the drawer's `alerts` list also carries its guests' alerts by node name. - Offline or stale nodes, last-known or unknown memory, and unmeasured disks show as not current or last known, never as live values or filled-in zeros. - Ranges use bucket min/max, so a spike averaged away inside a bucket still shows (delly's CPU temperature reads 42–92°C, not 44–73°C). - A failed refresh says it is showing the last loaded trend. **Governance:** amends the `frontend-primitives` rule that curated drawer facts must not need another tap, for these two drawers only. Recorded as a named bet in the demand ledger (rcourtman/pulse-pro#419), graded at +30 days. Contract notes in `frontend-primitives`, `performance-and-scalability` and `unified-resources`. **Verification:** - Full frontend suite: 23,213 passed. Lint, typecheck, production build and bundle budget pass (`useWorkloadsState` 55.88 kB of 70.23 kB). - Six negative controls: reverting each fix fails its targeted test. - Browser pass on the real homelab estate at 1280, 1024 and 390px. The receipt is in `frontend-modern/browser-verification/`.
Pulse documentation
Start here for installation, platform setup, security, operations, and Pulse Intelligence. Commands, configuration keys, image names, API fields, and product identifiers remain untranslated in localized guides.
Need help with a failure? Read the safe reporting guidance before sharing evidence. A second reproduction or diagnostics export is not required; keep the original evidence if another attempt could interrupt workloads or send duplicate notifications. GitHub reports and attachments are public: review them locally and keep credentials and private details out.
Start here
- Install Pulse — signed Proxmox/Linux installation, Docker, Docker Compose, Kubernetes, and first-run setup.
- Production deployment and security — least-privilege Proxmox setup, root-agent boundaries, discovery, supply-chain verification, plan limits, scale evidence, and a rollout checklist.
- Upgrade from Pulse v5 — migration prerequisites, rollback, agent continuity, and post-upgrade checks.
- Releases and update channels: choosing Stable or Preview, beta and RC expectations, and how releases are tested and promoted.
- Configure Pulse — authentication, notifications, discovery, retention, and system settings.
- Deployment models — data locations, lifecycle, and differences between supported deployment paths.
- Troubleshooting and FAQ — common failures, diagnostics, and operator questions.
Localized getting started guides: Deutsch · Español
Platforms and agents
- Proxmox Backup Server
- Proxmox Mail Gateway
- Docker and Podman
- Kubernetes and Helm
- TrueNAS SCALE and CORE
- Unified Agent
- Agent security
- VM disk monitoring
- ZFS monitoring
- Temperature monitoring
VMware vSphere support is early access. Current builds expose dedicated vSphere inventory and recovery context, but operators should validate the integration against their own vCenter before production use.
Monitoring and operations
- Metrics history
- Recovery data
- Webhooks
- Automatic updates
- Centralized agent management (Pro)
- Operational trust model
- Current product screenshots
Pulse Intelligence
- Assistant, Patrol, and external-agent overview
- Patrol modes and safety
- Assistant safety model
- External agent HTTP and MCP substrate
Patrol watch-only analysis is available on Community with a local model or the operator's own provider. Investigation and governed fixes require the relevant Pulse Pro capabilities.
Security, privacy, and access
- Production deployment and security
- Security review scope
- Authentication and credential storage review packet
- Security guide
- Privacy and telemetry disclosure
- OIDC and SSO
- Proxy authentication
- Role-based access control (Pro)
- Audit logging (Pro)
- Reverse proxy configuration
- Code-signing policy
Plans and managed access
- Community, Relay, and Pro capabilities
- Relay and Pulse Mobile handoff
- Multi-tenant organizations (Enterprise/custom)
- Provider-hosted MSP operations (request-assisted)
Pulse Cloud is not generally available. Ordinary self-hosted Pulse remains the primary installation path; MSP and Enterprise access are explicit commercial paths rather than defaults in self-hosted setup.
Development and reference
Detailed design notes and dated migration specifications may remain in this directory for maintainers, but they are not operator setup guides unless they are linked from the sections above.
Previous versions and migrations
- Upgrade from v4 to v5
- Retired unified-navigation migration — historical context only; current Pulse uses platform-shaped navigation.
- Move a Pulse installation
Found a bug? Use the issue forms. For setup questions, use GitHub Discussions.