mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-25 21:20:00 +00:00
pulse-triage[bot]
9fb404604b
Improvement: backup-age false-recovery repair now has executable and desktop/phone pixel proof. **Continuation — truthful monitoring and backup evidence.** Candidate **6fb43d9302d6673bc65193f3e17944098394ad6d**, above **c67f8bd500**, contains **208f0cbf1e** plus an additive fixture correction. Original-runtime control reproduces false recovery; full alert race/vet, final consumer type checks, **1,404 tests**, compiled real Overview and both browser journeys pass. Complete output hashes match, source guests stopped, and all eight captures were natively opened and inspected. Coordinator/reviewer/publisher own containing CI, independent review and landing; their containing result or repair return is next. **Not landed, released or installed recovery.** [Receipts](RECEIPTS.md), [source](SOURCE.json), [continuation](CONTINUATION.json). This raises the highest-ranked **guest/backup safety** weakness: a still-listed backup's missing/zero/future date no longer clears an established warning or hides valid provider evidence. Last trusted occurrence/evidence survives; valid recent success, exclusions and authoritative removal still clear normally. The executed baseline establishes the defect, not a field incident's cause or native thaw safety. [Reproduction](REPRODUCTION.json), [scope and original jobs](RECONCILIATION.json). The first consumer proof exposed a fixture-only type error; the additive correction uses the current AI capability store without changing production code or weakening checks. Both commits pass canonical preflight; the frontend-file guard skip is not the separately completed browser proof. [Validation](VALIDATION.json), [adverse evidence](ADVERSE.json), [pixels](PIXEL-REVIEW.json). Received continuations **416bb1c9 / 58e731f1** are completed at the source-validation step. Previous node candidate **3c66ab14e7** and Delivery/Pro/Host/PI's original installed guest, dashboard, SSO and notification recoveries remain separately retained. No duplicate handoff, infrastructure, guest probe, excluded investigation, release or public action. --- Fleet candidate `20261023T172026Z-core-runtime` from the `core-runtime` lane. Reviewed tip `6fb43d9302d6673bc65193f3e17944098394ad6d` on `main`. [How Pulse handles triage](https://github.com/rcourtman/Pulse/blob/main/docs/AI_TRANSPARENCY.md)
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.