rcourtman
1120502a1d
The Patrol inbox passed each alert's own resource reference through as the item subject: docker:<host>/<container> for a Docker container, <instance>:<node>:<vmid> for a guest, agent:<host>/disk:<label> for a filesystem. Patrol findings, protection postures and resource actions carry the unified resource ID instead, so "Browse Patrol findings for this resource" opened an empty list, postures never attached, and the alert detail said Patrol had raised no finding while it had one on that exact container. The attention projection now resolves each record's subject through the org registry's alert reference resolver and names the unified resource. The operational record keeps the alert's reference, and a reference inventory cannot bind stays as before. The resolver gains Docker container references with a complete ID, the key RecordChange already joins their history to, so container alerts resolve like every other kind and alert-triggered Patrol scopes for them keep the triggering alert. It also reads source targets from the registry's view cache rather than scanning every mapping per reference, which a page of alerts would otherwise multiply. The alert-mirror reconcile compared the same mismatched strings and never folded a finding under its alert; it now matches either identity. A filesystem, sensor or ZFS pool alert resolves only to the owner its siblings share, so the resolver marks it as a component and the reconcile does not match on that owner. The inbox links a finding to the exact alert it restates by the stamped alert ID, not by resource and kind, which several alerts on one host share. The restart offer checks evidence against the record's own reference, since the item subject is now the unified container its registry lookup needs. When no finding restates the alert but Patrol has open findings on the same resource, the detail names them instead of saying Patrol raised nothing, and the browse button appears only when there is something to browse.
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.