mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-09-10 02:25:56 +00:00
Richard Courtman
12e833d3d0
72 installs delivered no notification at all in the week to 2026-09-03 and between them burned 196,562 attempts for 62,618 dead letters. Their categorised failures are 79% authentication (11,693), configuration (9,554) and rejected (5,954) against 930 connectivity: deterministic verdicts about the request, not conditions that clear. The queue retried each of them the full ladder anyway, because the retry decision never consulted the failure class. Those three classes now dead-letter on the attempt that produced them. The same payload, sent again to the same destination with the same credentials, gets the same answer; spending two more attempts on it only delays the dead letter the operator needs to act on. Connectivity, rate limiting, server errors and unclassified failures keep the full ladder. TLS deliberately stays on the retrying side. A handshake can fail transiently during a rotation, and one wasted ladder is cheaper than dropping a recoverable notification. This is the same call webhook delivery already made for HTTP 4xx in isRetryableWebhookError, now generalised to every destination type and owned in one place. It was not safely expressible before the class became sender-declared rather than guessed from error prose. Nothing is lost by giving up sooner: RetryTerminalFailures still returns retained terminal failures to the queue with a fresh budget once the operator fixes the credentials or the configuration, and dead-letter rows now record the failure class and whether the cause was an exhausted ladder or a non-retryable class. Note for telemetry reads: notification_attempts_7d will fall sharply in the blackout cohort while notification_failures_7d is unchanged, because the same terminal failures now cost one attempt instead of three. That is the intended effect and not a drop in notification volume.
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.