mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-24 04:33:17 +00:00
pulse-triage[bot]
1d4c3aeb6e
## What changes and why Keep guest monitoring truthful while reads are deferred: retained memory/filesystem values must not become new alert decisions, new History observations, current filesystem health, or continuous chart lines across missing readings. Failed or empty metadata refreshes retain the last useful observation time rather than manufacturing freshness. Independent current readings and measured-zero recovery keep their existing behaviour. Manual guest Discovery pauses during the existing backup/read precaution, preserves saved evidence, and keeps delayed outcomes attached to their original guest and run. The published drawer-header link to a saved web interface remains available separately from live Discovery. The existing TrueNAS guide and shipped copy keep credentials and responses private and bound individual requests. The guest work follows the prolonged freeze reported in #2439 and reproduced downstream observation/lifecycle gaps. It does not identify the freeze's cause or prove native recovery. The guidance repair follows inspection of unsafe existing recipes. No new collector, schema, retention policy, threshold or product surface is introduced by this batch. ## Included source and reconciliation Current published base `efe6fc21ae10a6bf173cc17e6203aaf6c97dc130` → proposed head `1914f5fb7b278b5fc4cc10a292e909a10714a2f8` (39 introduced commits, including additive integrations). - TrueNAS guidance: `cadfd1f4e1d9f909a45977f94aadd4f1324e82ef` → `d589407a743a12fe492e93785d9e24c12bbb4fb5`. - Discovery pause/outcome ownership: `2cb3f6a9043e0bab9c54c5b5ef57b3e1cb994781` → `bbaee0a3f43dc7906011be5c78d684f9a1327bae`, including additive recovery and lifecycle controls. - Alert admission: `b0f8b96c8a159ac242b85f2d09f8dfffd5c29c7a` → `0fd7768e9d1379f8aa0126b33d4047b4c52c0d87`. - History writer admission: `a15920eaebea00ab8c353ddd3861b9cd7ff7d379`. - Filesystem presentation: `2525d76c04a9834c2130e97c1a529e164a9c7796` → `5b75f21159fda3c01fbe6688aa9cfde68779fba8`. - Metadata freshness: `f1e221a0fb9b0804f200c13490f8526424cb7e1c`. - Missing-observation chart presentation: `0ad41e4c9a309ce459dd717d16d343b46efcac8a` → `5e7e49650fcdf5131b7c5006fe487336ab660e15`. - Platform-aware Discovery fixture: `a2608c9fadf76c242527a636ee08968fa16ddde8`; TrueNAS recipe reconciliation `1f0d12af85ec7c2ad8df391b8e6958e80fa98179`; additive upstream/header composition and content-bound browser receipts through `b01dad904c3436e70bc01588ea1546fffaa05dc6`; batch-start upstream merge `f1c7e413bac2e3306d2169bcd069c60325e56d5f`, then exact bounded refreshed-upstream merges `07112b0e3ab2be174a5ac7a11f87ac0837edceb0` and `1914f5fb7b278b5fc4cc10a292e909a10714a2f8`. The previous proposal head `6a20d106242598bd6b466e9ae888ea931d284b30` is completed-failed, not still validating. Native run `37239183481` incorrectly required a Linux/PVE capability on Windows/macOS; Build and Test `37239183545` extracted zero wrapped TrueNAS recipes. Reviewed additive fixtures correct both without weakening runtime safety. The old head cannot land independently, so this update includes those corrections and the coherent observation batch. Every accepted commit identity and all ancestry are retained. Published cluster labels, saved guest links, unique demo workload names the newer storage priority/alert explanations, and the published Alerts overview are preserved. Bounded refresh receipt `2916978f4e4b49d084752e973e19a5c0f7dd19f0bf4ac60cc31875876318528d` completed at the exact observed upstream without changing source; the subsequent full-SHA merge composes it additively. A second successful bounded refresh `59f1939979347921d99e262398d5347077bfce6faf6f42535050840a3a19820b` incorporates the subsequently published Alerts overview in the same way. Neither is a replay of a failed or uncertain attempt. ## Validation and remaining gates Retained evidence includes connected alert/API/producer/recovery controls (`source-p58_phvc`), Discovery/component/build/browser checks (`source-gy5x8buj`), installer/docs controls (`source-7s0iorys`, `source-uo6rxs61`), metadata connected/race/vet/build proof (`source-ji23nb_c`), and ten connected suites plus focused safety races/vet and native-target compilation (`source-seboen4h`). Browser content receipts cover the final seven changed frontend runtime files, including the composed saved-link/safety header and chart gaps. The History presentation proof `source-ualisb1k` completed 22,571 frontend tests across 1,234 files, types/lint/format/build and bundle/integrity checks; its overall exit 1 from trailing nonexistent optional test paths remains recorded, not converted into a whole-command pass. Four browser groups/32 checks and eight inspected captures separately passed. Earlier reproductions, fixture failures and reporting-limit failures remain evidence. Publication-gate checks: - `source-qt6m6mf_`: seven connected TrueNAS recipe controls, full mock suite, scoped real agent/guest safety, alert observation and metadata/History tests pass. Backend/docs source is byte-identical in the final composition; this evidence was not repeated after frontend-only upstream advances. - `source-xy1lnmgt`: types pass and 281 of 283 scoped frontend controls pass; two first-case History tests hit the unchanged 5,000ms timeout. Exit 1 is retained and the following build did not run. No functional assertion failure or cause was established. - One predeclared single-worker/file-serial comparison, `source-17bch24o`, passes all 23 controls in those two files with unchanged source, assertions and timeouts. This establishes isolated functional behaviour, not a diagnosis or clearance of parallel CI. - `source-dvlfnm5t`: refreshed storage composition passes types, 1,177 tests/56 files and the real production/embed build. The event-parser line-bound flag is recorded; the complete 26,474 raw bytes independently match the receipt. - Final exact-head `source-sjjtzjqm`: types, scoped published Alerts overview/translation/presentation controls and the real production/embed build pass. Complete raw output is independently hash-matched and the guest stopped. - All executed receipts, including the failed scoped run, retain complete output and completed guest stop. Provenance, clean source, diff/ancestry checks, all 24 introduced non-merge commits' parent-bound canonical guards using only their original recorded trailers, and the final seven-file browser-content receipt guard pass. Required exact-head administrative source review and GitHub checks must complete before landing; this update is not a blind failed-job retry or a CI waiver. Native overlap, independent thaw, fresh writes on every covered filesystem, workload liveness, truthful alert delivery and safe restoration of only prior-active services/timers remain separate. UI clearance, saved values, an OK backup or these source tests are not recovery, a containing release or installed/reporter acceptance. Related to #2439 [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.