mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-25 04:59:43 +00:00
rcourtman
55b6e5145e
Stacked on #2686 (which is stacked on #2682). It lands after them. ## Problem Patrol > Activity > Finding options and history > Open work showed **Check needed: Run Patrol to check everything and refresh open work.** whenever `overall_health.factors` held any `coverage` factor. After a clean full run, the backend keeps its `Recent Patrol errors` coverage factor if an earlier run in its 24-hour window errored (`summarizeRecentPatrolCoverage`). It drops the factor only when three clean full runs lead that window or the errored runs age out. At the default 6-hour interval that left about 12 hours of "Check needed" after a clean check of every resource, while the header read `Last check: 4m ago · checked 1377 resources`. One press of Check now did not clear it. At impact 20 or 30 the factor lowers the grade to B or C, so the same stale signal showed **Patrol needs review** instead. ## Change - `getPatrolFindingsEmptyState` reads run history first, through the new `getPatrolRunCoverage`: - **complete**: the latest completed full run ended cleanly, checked resources, finished within the last 24 hours (the backend's window), and no run after it failed. A coverage factor no longer withholds the all-clear, and a grade lowered only by coverage factors no longer counts as degraded health. - **incomplete**: the latest full run, or a run after it, ended with errors, or only targeted or follow-up runs have completed. Shows "Check needed". A failed targeted run after the last clean full run is new here: it used to read green whenever the backend had dropped its factor. - **unproven**: no completed run, or a clean full run that checked nothing or finished more than 24 hours ago. The coverage factor decides, as before. - `getPatrolVerificationPresentation` was read only for its warning tone. `getPatrolRunCoverage` replaces it. The activity-mix label had no reader, so it goes, along with `getPatrolActivityBreakdown` / `formatPatrolActivityBreakdown`, whose only caller it was. - The backend factor and its three-run rule (documented in ai-runtime) are unchanged. - patrol-intelligence, api-contracts and frontend-primitives now describe the reconciliation. ## Verification - Vitest over `src/utils src/features src/components/AI src/components/patrol src/components/shared src/pages src/hooks src/__tests__`: all pass except `agentInstallCommand.test.ts`, which fails on the Mac regardless of this change, and one `DockerHostsTable` case that timed out under load and passes on its own. The new empty-state cases fail against the parent tree. - Browser: embedded builds of the parent (#2686) and this tree on private DEMO_MODE stacks, with run history and overall health stubbed, at desktop 1440x1000 and phone 390x844. Eleven scenarios per width, including Check now while the factor is present. Results are in the receipt.
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.