rcourtman
c0948cf792
Proxmox's `/cluster/resources` `mem` for a container is its cgroup usage with page cache already subtracted (`PVE::CGroup::get_memory_stat`: `memory.current - memory.stat file` on cgroup v2, `usage_in_bytes - total_cache` on v1). #3011 makes the backend read it as known pressure for containers. The frontend still listed `cluster-resources` as cache-inclusive for every guest, so the container drawer said the reading "may include cached memory the container can reuse" and appended agent setup advice. - `memoryObservation.ts` classifies `cluster-resources` by guest kind: cache-excluded for a container, cache-inclusive for a QEMU guest or a guest of unknown kind. The other Proxmox fallbacks are unchanged. - The canonical resource drawer (`resourceDetailDrawerMetricsHistoryModel.ts`) now passes the guest kind, so it qualifies the same reading the same way. A retained VM reading there also gets the VM wording the Workloads drawer already uses. - The frontend-primitives contract clause that said a container's Proxmox reading always carries the caveat is corrected. Tests: the new container cases in `memoryObservation.test.ts`, `GuestDrawerOverview.memory-cache.test.tsx`, `GuestRow.test.tsx` and `resourceDetailDrawerMetricsHistoryModel.branchcov0712.test.ts` fail against main's source (6 failures) and pass with the fix. Existing container-copy tests now use `status-mem`, which is still cache-inclusive. Browser pass: private mock backend built from main. Before the fix, LXC `auth-service-01` (`cluster-resources`) showed `Current · Proxmox (may include cache)` and an `About this reading` note. After the fix it shows `Current · Proxmox` with no note. A QEMU drawer keeps its caveat. Checked at 1440 and 390 px wide. Refs #2762
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.