mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-24 04:33:17 +00:00
pulse-triage[bot]
74fd189fd0
## What changed and why Alert cleanup now retires an expired flapping episode together with its suppression deadline. Previously either cleanup owner could remove the deadline but leave the episode latched, suppressing notifications without a newly bounded cooldown. Active alert identity, unexpired suppression and ordinary repeat-notification cooldown remain unchanged. TrueNAS troubleshooting now distinguishes stale polling, missing telemetry, authentication failures and session turnover. The existing guides preserve polling evidence before a manual connection test updates timestamps, use the actual 60-second default and avoid credential resets or destructive reproductions. This addresses the diagnostic gaps exposed by #2382, #2396 and #2400; it does not claim those native incidents are all resolved. ## Reviewed source included Complete unpublished range: `0e90236d3bb901dc84d4d07e70d4d2a09d5e6705..971ebde8afdc0f55dd0ea77a0358467caf62ea73` (five commits, including additive integration history). - TrueNAS guide candidate `4b0f23e0a7a7d03df391f83896cbf4b48657bd24` (2 October). - Alert cleanup candidate `d813c936e464eb09bb9ae7e6c7ac33716acde378` (2 October). - Integration tips `e9294420`, `71382de0`, `971ebde8` preserve the original candidates and published main ancestry without rewriting them. ## Validation - Accepted alert candidate evidence: six parent-failing cleanup cases pass on final; full alerts correctness/races, ten focused race repeats, notification correctness, library vet/build and 132 governance checks pass. The integrated alert files are identical to that candidate. These proofs used Go 1.26.7; declared Go 1.26.8 CI remains required. - Accepted guide evidence: seven guide checks, three polling controls and 25 Docs/viewer tests; desktop Chromium and phone WebKit navigation/readability checks. Integrated guide/test files are unchanged from that candidate. - Exact combined head: seven guide checks pass in offline source proof `source-x4fm8fxy`, exit 0, complete output and completed guest shutdown. The preceding confined lightweight attempt could not create loopback sockets (five errors); it is an execution-context limitation, not a pass. - Publication provenance and whitespace checks pass; live main matches the range base. Required exact-head CI and independent source review still gate landing. Real-duration alert queue/HTTP acceptance remains with its existing owner after an interrupted proof; native monitoring acceptance and containing-release delivery remain separate. No release, tag or deployment is changed by this PR. [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.
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.