mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-26 13:39:47 +00:00
pulse-triage[bot]
e1e2860d35
Scrolling through a long platform drawer could unmount its owning row and close the detail being read. REST resource projection also dropped source provenance, hiding vCenter context and host placement from owning-snapshot consumers. Diagnostic commands lacked keyboard scrolling, and dark-theme text and several Patrol control names failed accessibility checks. Measure summary rows and inline details together in the shared bounded window, preserve canonical resource sources, make diagnostic command blocks focusable, and repair shared contrast and visible control naming. Browser fixtures await mounted authentication and keep synthetic provider inventory authoritative. Journey assertions follow current read-only capabilities, technical disclosures and composed resource queries. Long settings audits traverse the actual scroll extent; curated estate checks use native inventory disclosures and search; disk proofs follow canonical serial-bound shared history; the published completed-restore-point calendar checks remain intact, including day selection and filter reset. Update API proofs no longer mount an unrelated dashboard before each request. Fresh password login now waits for mounted bootstrap too. The delayed-bootstrap regression owns and revokes its own token, so it runs with cookie-only and primary-token fixtures without replacing the fixture credential. Update API cases share an admitted cookie fixture. Growth assertions use the current fixed-window header, LXC refresh assertions use the fixture's canonical identity, and the gated-panel observer follows actual gate readiness while still detecting visible unlocked controls. The Docker browser stack explicitly opts into a bounded development update budget for its shared bridge IP. Production and login limits remain unchanged. The remaining recovered failures exposed three test synchronization defects. Alerts now leaves the whole editor before judging a staged change and exercises its sibling-focus contract. Protected panel assertions wait for mounted bootstrap before their existing readiness timeout. The delayed-token regression uses its own page, avoiding interception of reads from a departing setup document. CI retains failed-attempt HTML diagnostics after a successful retry and small JUnit results for each completed tier, including stable receipts before probation starts. Validation includes negative controls for the original drawer, provenance and password-bootstrap defects, 335 focused frontend tests, 23 authentication-fixture tests, type-checking and a production build. The cookie-only follow-up matrix passed 39 cases across Chromium, mobile Chrome and mobile Safari with 18 existing skips. Twelve additional onboarding cases passed with no retries, and the token-bootstrap matrix passed 12 cases with cookies alone and 12 with a primary token. Native Chromium and WebKit checks exercise the gated-panel detector's positive and negative controls. The earlier remaining-failures matrix passed 31 cases with 10 existing skips, and both disk-history cases passed on desktop. Current-build browser verification covers onboarding, accessibility, VMware context and exclusion boundaries, demo commercial isolation, persisted Alerts settings, Patrol, availability and background refresh. Pixel and interaction review covers infrastructure, Agent Doctor, Patrol, Docker, Kubernetes and vSphere at desktop, tablet and phone widths in both themes where applicable. Existing timeouts, skips, mounted-row limits and the 90 ms chart budget remain in place. The final recovered-failure matrix passed 27 cases with 14 existing mobile skips using cookies alone, followed by 12 passes with a primary token, all without retries. The forced desktop table control reproduces the old focus failure and passes after leaving the editor. The preceding qualified tree completed all required source checks and the full stable/probation matrix. Its executed strict chart proof measured p95 61.1 ms against 90 ms with valid capacity. The updated head is being qualified again before landing. Governed work: L12 journey verification and the shared L10 windowing proof. This source change does not publish a release.
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.