pulse-triage[bot]
be25170ee1
**Back off optional Proxmox permission-denied reads** Keep typed HTTP 403 denials on the existing 30-minute APT and five-minute guest-memory negative intervals, without promoting stale or absent observations. Preserve successful clocks, independent target scopes, ordinary transient retries and guest lifecycle/uncertainty fences. Cover direct and cluster transports, expiry, recovery, zero evidence and shared runtime separation. Report and patch reference: Pulse #3546 by @tyvsmith; this candidate implements the scoped repair from current source. Reported-by: tyvsmith **Keep Proxmox update recovery zeros explicit on the wire** Consuming browser proof for #3546 exposed a connected recovery failure: the canonical merge retained seven stale updates and its access reason when a successful empty response omitted zero and empty fields. Emit the complete existing count/status/reason/origin tuple for an explicit node verdict, preserving guest and legacy payloads. Register JSON merge, API/realtime and legacy controls with precise ownership. This fixes the changed producer through the existing consuming surface without a frontend, permission or cadence change. **Keep SSO provider labels on complete UTF-8 boundaries** Preserve the existing 128-byte cap without slicing a valid code point into invented replacement characters. Keep trim/control order and intentional replacement characters, and cover byte-boundary cases, registered Community HTTP writes and persisted/list/detail/login discovery, redaction, stable IDs and presentation-only runtime reuse. Register the focused SSO management proof route. Contract-Neutral: Restore valid UTF-8 within the existing 128-byte label cap; API shapes, byte limit, trim/control rules, IDs, credentials, authorisation and runtime-reuse contracts are unchanged. **Keep SSO verification paths in canonical order** The first composed source proof passed all 131 SSO/API race roots, vet and the native consuming exporter, but the registry's sorted-path invariant failed on the new SSO policy. Sort the same exact six proof paths; preserve their scope and every runtime byte. Contract-Neutral: Verification-path ordering only; runtime, API, proof selection, contract and frontend content are unchanged. --- Fleet candidate `20261030T064533Z-core-runtime` from the `core-runtime` lane. Reviewed tip `3279b66588c06775ef6d5aab0a868d4e055a8602` 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.
The local guides below are shipped with this installation. Links labelled GitHub or online open online resources in a new tab and need network access; their current content can differ from your installed version.
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
- Live demo (online) — generated sample data, not a real deployment.
Pulse Intelligence
- Assistant, Patrol, and external-agent overview
- Patrol modes and safety
- Assistant safety model
- External agent HTTP and MCP substrate
- Walkthrough: what happened overnight on my Proxmox and Docker fleet?
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 (self-serve evaluation and purchase)
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
- REST API
- Architecture
- Contributing
- Published release notes (GitHub)
- Development transparency disclosure
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.