mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-24 04:33:17 +00:00
rcourtman
68df09104b
## What was wrong The metric, stacked memory and stacked disk bars choose between `60%` and `60% (265 GB/440 GB)` by estimating the label's width. The estimate was 5.5px per character plus 8. At the label's 10px type a digit is 6.7px wide and a full stop 3px, so the estimate was off by -7px to +5px on real labels. In the Kubernetes clusters table at a 560px viewport the memory bar is 113px wide, the estimate came to 112.5px, the label needs 118px, and it rendered with an ellipsis. A sweep of the platform tables found 24 such bars on `main`, all stacked memory bars: 3 on Kubernetes clusters at 560px, 4 on Proxmox overview at 900px, 16 on Docker overview and 1 on Kubernetes nodes at 1440px. ## The fix `estimateTextWidth` sums per-glyph advances instead of multiplying a character count. - It reads the advances once per page from a hidden probe that carries the label's type classes, so the estimate follows whichever system font the browser renders. The advances measured for the macOS system font stand in where there is no layout (unit tests). - The value is measured semibold and the detail after it at normal weight. - Each model adds the padding its own label sits in (4px in the metric and disk bars, 8px in the memory bar's chip) instead of sharing one constant. Two more gaps in the same decision are closed: - The stacked memory and disk bars now count the anomaly marker that shares the label's line. - The inline per-disk slots are sized after the gap between them. A two-disk Proxmox node at 900px clipped `backup 80%` by 2px. A flat safety margin was not enough: the error depends on which glyphs the label holds, so a margin that stops the clipping also hides labels that fit. Measuring each label in the DOM would add a layout read per bar on the Workloads hot path. ## Verification Playwright sweep of every table on 32 platform routes at 1440, 900, 700, 560 and 390px (160 loads, 2,579 bars), on this branch and on `main` against the same mock backend: | | `main` | this branch | | --- | --- | --- | | Bars whose chosen label does not fit | 24 | 0 | | Clipped inline disk labels | 3 | 0 | | Bars showing the long label | 567 | 550 | Of the 17 fewer long labels, 24 are the clipped ones, 14 Proxmox guest disk bars at 900px gained the long form, and 7 memory bars dropped it: 5 that had 1.0px to 2.8px to spare and 2 that overflowed by under 0.5px. With every glyph forced to Verdana (10% wider) no bar clips; with Arial (7% narrower) no bar clips and 237 more show the long label. WebKit matches Chromium. The probe is the estimator's only layout read: 1.7ms on the 429-bar Proxmox overview, about 110ns per estimate afterwards. Bar widths still come from the resize observer alone. ## Not changed here The storage usage bar on Proxmox > Storage still clips at 390px (72 rows) and by up to 2.3px at 700px (19 rows). It is a different component that always renders the long label and does not use the estimator; #2418 reworks it.
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.
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.