Files
pulse/docs
rcourtman bd54435e24 Unify alert metric editing across responsive layouts
Numeric threshold controls had four implementations. Desktop input blur
could save a draft before Cancel ran, and resizing could save the draft
while replacing the table with cards.

Share the numeric editor, keep focus changes within the owning row, and
transfer draft and metric focus when the active layout changes. Stack
sliders above inputs so editing fits the table. Preserve cluster context
on host cards and keep backup/snapshot configuration out of numeric
defaults. Cleared overrides resolve inherited Off for both badge and slider, and
one toggle enables a factory threshold when the parent is Off. Existing
Off, inherit and persistence contracts stay intact.

Verified with 209 targeted tests, type-checking, builds and current-build
browser checks across desktop, intermediate and phone widths.
2026-10-12 15:49:49 +01:00
..
2026-10-12 14:10:58 +01:00
2026-10-12 14:10:58 +01:00
2026-10-12 14:10:58 +01:00

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

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

Pulse Intelligence

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

Plans and managed access

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

Found a bug? Use the issue forms. For setup questions, use GitHub Discussions.