rcourtman
8f10dfa943
Configured report schedules and recent attempts do not show successful delivery or repeat use. Add durable aggregate reporting counters to the existing opt-out-controlled heartbeat, covering resources, VM inventory, backup health and Patrol digests. Count successful generation, saved files, SMTP acceptance, definite delivery failures and uncertain acceptance separately. Track distinct successful saved-schedule periods and active days, including manual downloads. Deduplicate retries and same-period reruns for repeat-period counts. The adoption report distinguishes unmeasured senders and partial observation from measured zero use. Generation across multiple days is reported separately from successful repeat periods because it can include retries. No report contents, recipients, raw schedule or tenant identifiers, scopes, errors or date ranges enter these new telemetry fields. Mock activity is suppressed. Pricing, billing, customer entitlements and the existing outbound opt-out remain unchanged. Update the schema-v20 disclosure and privacy document. The shared telemetry observer has an exact-path adapter declaration. Boundary regression fixtures reject sibling reporting implementation and private licensing imports. Validation: reporting persistence, API delivery/retry/restart and successful-write tests, server snapshot tests, the full telemetry package, 45 adoption-report tests, frontend type-check and build, and governance audits passed. The three telemetry browser tests and a separate pixel interaction check passed against the final source at 1280, 390 and 768 pixels, including saved opt-out states and the privacy table. Source-bound browser receipt included. Companion receiver: rcourtman/pulse-pro#472. Receiver deployment and a client release are separate activation steps. This change alone does not start production collection.
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.