mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-24 12:42:49 +00:00
rcourtman
3b290640a5
Follow-up to #2575. The Docker host and Machines drawers list a resource's open alerts through `getAlertsForUnifiedResource`, but their table rows matched alerts differently, so a row could look healthy while its drawer said "Needs attention". - **Docker hosts:** rows called `getAlertStyles(host.id, …, host.name)`. Docker alerts are keyed `docker:<host source id>[/…]` and carry the hostname as their node, so a host whose display name differs from its hostname was never highlighted. Example on the mock estate: "Ops Services 01" (ops-services-01, source orion-2-mock) had three open service-health alerts and no highlight. - **Machines:** rows had no alert highlighting, so a machine with an open `agent:<id>` memory alert looked normal until its drawer was opened. `getUnifiedResourceAlertStyles` computes the existing row styles from the same set the drawer lists. Both tables now use it with the red/yellow tint the other platform host rows use: unacknowledged alerts only, and not on an expanded row. `getAlertStyles` keeps its id-plus-node matching for the tables whose alerts are keyed that way. **Verification** - Unit tests: the helper with Docker, agent, acknowledged-only and detection-off cases. Docker host rows are checked against their own drawer. Machines rows follow the live alert store through acknowledge, escalation and resolution. Both table tests fail on the previous table code. - Private mock stack (embedded build of this tree): every Docker host and machine row tinted exactly when its drawer lists an unacknowledged alert, at 1440px and 390px in light and dark. Acknowledging Apollo-114's memory alert from the Alerts page clears its row tint while the drawer keeps it as Acknowledged. Receipt: `frontend-modern/browser-verification/18ad64507908105c.json`.
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.