mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-09-10 02:25:56 +00:00
rcourtman
a10c175f31
Two users (discussions #1623, #1699) could not find Patrol's durable outcomes: the Needs attention detail offered only Acknowledge and Suppress, and Remember as expected, Dismiss: Not an issue, Dismiss: Later, and Create rule sat two levels below it. The same screenshot showed an alert with eleven open/resolved transitions in a day listed as eleven timeline rows, and Patrol findings restating an active alert appearing beside it. Telemetry shows most findings are seen and ignored. Backend: findings_alert_mirror.go is the single matcher for a finding that restates an active alert (explicit alert identifier, or same canonical resource plus the same condition class). Patrol stamps mirrors_alert_id/mirrors_alert_type after every real and demo cycle and clears them when the alert resolves; the finding is kept, not dropped. The storm throttler now also owns flap detection: four or more open/resolved transitions in 24h mark a finding flapping, and the store maintains one collapsed lifecycle row with the count instead of a row per transition, hydrating the window from persisted lifecycle after restart. The attention projection applies the same threshold to alert timelines and exposes a flapping summary while keeping the full timeline. Frontend: the attention detail gains a Lasting decisions section that offers the four Patrol decisions on the finding mirroring the alert, each with one line saying what it does and how long it lasts, an inline confirmation, and a remembered-decision state with Reopen. An alert with no mirrored finding says Patrol has nothing to remember and points at alert thresholds. Flapping items carry one label and a summarised timeline with every transition under an expansion. FindingsPanel demotes active alert-mirroring findings into a collapsed group. The Patrol surface loads dismissed findings so remembered decisions are visible.
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.
- 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.