Pulse/docs
pulse-triage[bot] 76e1aea061 Make notification troubleshooting bounded and delivery-aware
Use the existing delivery activity and failure classes before collecting raw logs. Keep both Docker streams and log-reader exits visible, warn about provider echoes and duplicate retries, and distinguish test success from real alert delivery. Exercise the copied bounded recipes and their unsafe predecessor with synthetic readers.

Change-source: pulse-maintainer
2026-10-02 00:28:59 +01:00
..
api
architecture Clarify contractor administration of customer-owned licences 2026-09-19 20:00:36 +01:00
i18n
images
monitoring
operations fix(ci): archive durable root-pair candidate 2026-09-10 19:13:29 +01:00
qualification Record incident history qualification and delivery 2026-09-08 03:20:20 +01:00
release-control Keep monitor bootstrap verification in canonical order 2026-10-01 23:10:43 +01:00
releases Keep authored release notes compatible with safety checks 2026-10-01 05:28:54 +01:00
security
security-review
AGENT_SECURITY.md
AGENT_SUBSTRATE.md
AI.md
AI_AUTONOMY.md
AI_PATROL_QUALIFICATION.md
AI_TRANSPARENCY.md Document standing maintainer reply and release authority 2026-09-08 10:00:11 +01:00
ALERT_ENGINE_EVOLUTION.md
API.md Integrate reviewed credential-safe administration guides 2026-10-01 09:36:28 +01:00
ASSISTANT_ARCHITECTURE.md
ASSISTANT_SAFETY.md
AUDIT_LOGGING.md Preserve audit evidence in verification and recovery guidance 2026-10-01 20:08:53 +01:00
AUTO_UPDATE.md docs: explain release channels and qualification 2026-09-08 12:51:15 +01:00
AVAILABILITY_HISTORY_CONTRACT.md
BACKUP_TASK_TIMELINE_CONTRACT.md
CANONICAL_ALERT_ENGINE_MIGRATION_2026-03-10.md
CENTRALIZED_MANAGEMENT.md
CLOUD.md Keep setup and metrics guidance credential-safe 2026-10-01 13:26:10 +01:00
CODE_SIGNING_POLICY.md
CONFIGURATION.md Preserve audit evidence in verification and recovery guidance 2026-10-01 20:08:53 +01:00
DEPLOYMENT_MODELS.md Preserve audit evidence in verification and recovery guidance 2026-10-01 20:08:53 +01:00
DOCKER.md
FAQ.md Keep FAQ and plan guidance aligned with Relay retirement 2026-10-01 15:28:12 +01:00
INSTALL.md docs: distinguish server releases from Helm helper results 2026-09-29 20:23:12 +01:00
ISSUE_TRIAGE.md Accept unsafe one-off failures in community intake 2026-09-29 19:24:42 +01:00
KUBERNETES.md Keep setup and metrics guidance credential-safe 2026-10-01 13:26:10 +01:00
MAIL_GATEWAY.md
METRICS_HISTORY.md Keep setup and metrics guidance credential-safe 2026-10-01 13:26:10 +01:00
MIGRATION.md
MIGRATION_UNIFIED_NAV.md
MSP.md docs(msp): verify published evaluation bundle guidance 2026-09-09 20:23:20 +01:00
MULTI_TENANT.md Align administration guide details with current handlers 2026-10-01 08:44:10 +01:00
OIDC.md
OIDC_SCOPE_GROUP_AUTH_FIX_SPEC.md
OPERATIONAL_TRUST.md
PATROL_ARCHITECTURE.md
PATROL_WEEKLY_DIGEST.md
PBS.md Make PBS setup and diagnostics credential-safe 2026-10-01 04:11:04 +01:00
PRIVACY.md fix(server): make local service-health probes dual-stack and bounded 2026-09-30 21:36:39 +01:00
PRODUCTION_SECURITY.md
PROXY_AUTH.md
PULSE_PRO.md Keep FAQ and plan guidance aligned with Relay retirement 2026-10-01 15:28:12 +01:00
RBAC.md Isolate administration guide session-revocation proof 2026-10-01 08:55:56 +01:00
README.md docs: explain release channels and qualification 2026-09-08 12:51:15 +01:00
RECOVERY.md
RELAY.md Keep security administration recipes credential-safe 2026-10-01 10:32:50 +01:00
RELEASE_NOTES.md
RELEASE_PROCESS.md docs: explain release channels and qualification 2026-09-08 12:51:15 +01:00
RELEASE_RESOURCE_EVIDENCE.md fix(release): mark store-history SLO measurement windows 2026-09-09 01:34:22 +01:00
REPO_BOUNDARY.md
REVERSE_PROXY.md
SCREENSHOTS.md
SECURITY.md
SECURITY_REVIEW.md
STORAGE_ARCHITECTURE.md
TEMPERATURE_MONITORING.md Keep agent setup tokens out of commands and unverified downloads 2026-10-01 05:41:44 +01:00
TROUBLESHOOTING.md Make notification troubleshooting bounded and delivery-aware 2026-10-02 00:28:59 +01:00
TRUENAS.md Explain how to find CORE graph responses without exposing a capture 2026-10-01 21:32:16 +01:00
UNIFIED_AGENT.md Distinguish command permission from a connected agent channel 2026-10-01 23:25:48 +01:00
UNIFIED_RESOURCES.md
UPGRADE_v5.md
UPGRADE_v6.md Preserve alert lifecycle truth and safe pinned updates 2026-09-24 17:43:50 +01:00
VM_DISK_MONITORING.md
WEBHOOKS.md
ZFS_MONITORING.md Clarify monitoring for unregistered Proxmox ZFS pools 2026-10-01 00:24:25 +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.

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.