rcourtman
bee3a94ce6
Patrol's post-run alert review skipped the model only for metric and
offline alerts that were still firing. Every other aged alert went to
the model with a context line of CPU, memory and status. On a private
Pro stack on 24 Oct 2026 the review resolved a docker-container-health
alert for a container Docker still reported unhealthy ("running with
normal CPU/Memory, no unhealthy indicator present"): the context never
showed health. The alert engine raised the alert again on the agent's
next report about 24 seconds later, so every Patrol pass flapped it,
with a resolved and a new alert and their notifications.
The still-firing gate now keeps, without a model call, the Docker
container alerts whose condition the container's current report still
carries, mirroring the alert engine's checks: a health result other
than healthy, starting or none while running; a runtime state the
state alert covers; exited or dead with OOM-killed set. A restart-loop
alert is kept while the container is caught in Docker's restart
backoff; the snapshot has no restart window, so a running container's
loop still goes to the model. The gate finds the container by the
alert's docker:<host>/<container> ID. Matching the display name, as the
lookup did, judged an alert against whichever same-named container
came first, possibly on another host.
The review context for a Docker container now carries its health,
restart count and OOM kill (yes, no or unknown), so a recovered
container's alert reaches the model with that evidence and still
resolves on its verdict. The prompt makes a condition the shown state
does not cover a KEEP, for alert types the gate and context do not
model yet. And an alert whose subject the context lookup cannot read
but inventory still holds, or holds the owner of, by durable identity
(a ZFS pool's storage, a guest's backup, a Swarm service) is described
as present, not as "not found (may have been removed)", which invited
a RESOLVE.
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.