mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-26 05:29:45 +00:00
rcourtman
de524e823d
Every Proxmox node and standalone Pulse agent is a unified `agent` resource in v6, and the Reports picker requests it as one. enrichReportRequest only enriched node, VM and container reports, so an agent report attached no alerts: on a mock stack, West Production A read HEALTHY, "All systems operating normally" and Quick Stats Alerts 0 while pve1 had two open critical node alerts. Docker runtimes, containers and Swarm services, storage, physical disks, Kubernetes, PBS and PMG reports had the same gap. Reports now attach the alerts raised under their subject's identities, read from its unified resource rather than host or node names: the unified and metrics-target IDs; for a machine, the linked Proxmox node's source ID and, when the agent source is present, the agent's "agent:<host>" alerts with their component children; the Docker alert producer's host, container and service references; a Proxmox storage pool's source ID with its ZFS pool and device children, or the agent alert on an Unraid array; and the Proxmox health and wearout alerts on a disk's device path only when they record that disk's serial, since a replacement disk takes over the path. A node alert that moved to the agent and the agent's own alert for that metric land in the same report, where pkg/reporting counts them once. Guests, storage pools and disks a machine hosts keep the alerts raised under their own identities on their own reports. Agent reports also fill resource details from the Proxmox and agent payloads and list the storage pools and physical disks whose unified parent is the machine. Disk rows for node and agent reports now share one builder, so both show only a collected temperature, coloured by the disk temperature alert thresholds.
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.