Pulse/docs
pulse-triage[bot] f293d6fe33 fix(release): mark store-history SLO measurement windows
The failed exact rehearsal buffered the store-history latency assertion, preventing resource telemetry from locating its actual test interval. Extend the existing exact API lifecycle allowlist and cover both targets with synthetic pass/fail fixtures without rerunning product qualification or changing thresholds. This is prospective observability, not clearance of the retained latency or crash evidence.

Change-source: pulse-maintainer
2026-09-09 01:34:22 +01:00
..
api
architecture
i18n
images
monitoring
operations ci: add fixed UUID layout diagnostic without release gate waiver 2026-09-06 22:11:03 +01:00
qualification Record incident history qualification and delivery 2026-09-08 03:20:20 +01:00
release-control Merge candidate 20260908T222519Z-web-product 2026-09-08 23:48:43 +01:00
releases Prepare v6.4.3-rc.1 release 2026-09-01 21:37:41 +01:00
security
security-review Point security disclosures at security@pulserelay.pro 2026-09-01 15:21:23 +01:00
AGENT_SECURITY.md Record rootless runtime qualification evidence 2026-09-01 22:09:22 +01:00
AGENT_SUBSTRATE.md Fail closed when installing MCP binaries 2026-08-30 05:11:55 +01:00
AI.md
AI_AUTONOMY.md
AI_PATROL_QUALIFICATION.md test(patrol): qualify bounded service storage failures 2026-09-06 06:04:56 +01:00
AI_TRANSPARENCY.md Document standing maintainer reply and release authority 2026-09-08 10:00:11 +01:00
ALERT_ENGINE_EVOLUTION.md Mark stale spec, plan, and contract docs with verified status 2026-09-01 20:43:26 +01:00
API.md Add the Patrol weekly digest endpoint 2026-09-02 08:53:50 +01:00
ASSISTANT_ARCHITECTURE.md Preserve canonical Patrol planning and outcome continuity 2026-09-07 17:24:25 +01:00
ASSISTANT_SAFETY.md Remove inferred Assistant continuation gates 2026-09-07 14:06:58 +01:00
AUDIT_LOGGING.md
AUTO_UPDATE.md docs: explain release channels and qualification 2026-09-08 12:51:15 +01:00
AVAILABILITY_HISTORY_CONTRACT.md Mark stale spec, plan, and contract docs with verified status 2026-09-01 20:43:26 +01:00
BACKUP_TASK_TIMELINE_CONTRACT.md Define backup task timeline contract 2026-08-31 16:00:47 +01:00
CANONICAL_ALERT_ENGINE_MIGRATION_2026-03-10.md docs: mark March alert-engine migration doc superseded in scope 2026-08-26 23:37:34 +01:00
CENTRALIZED_MANAGEMENT.md
CLOUD.md
CODE_SIGNING_POLICY.md Verify exact release activation bytes 2026-09-01 13:29:06 +01:00
CONFIGURATION.md Support agent retargeting after server moves 2026-08-30 16:17:15 +01:00
DEPLOYMENT_MODELS.md
DOCKER.md
FAQ.md Clarify development transparency policy 2026-08-26 09:24:57 +01:00
INSTALL.md Publish portable candidate build provenance 2026-08-30 20:34:04 +01:00
ISSUE_TRIAGE.md Preserve secondary issue feedback 2026-08-29 12:24:03 +01:00
KUBERNETES.md
MAIL_GATEWAY.md
METRICS_HISTORY.md
MIGRATION.md Document agent URL updates when the server address changes 2026-08-31 06:41:11 +01:00
MIGRATION_UNIFIED_NAV.md
MSP.md Email the Patrol weekly summary as a report schedule kind 2026-09-02 11:15:22 +01:00
MULTI_TENANT.md
OIDC.md Enforce explicit SSO administrator grants 2026-08-31 00:43:42 +01:00
OIDC_SCOPE_GROUP_AUTH_FIX_SPEC.md Mark stale spec, plan, and contract docs with verified status 2026-09-01 20:43:26 +01:00
OPERATIONAL_TRUST.md
PATROL_ARCHITECTURE.md
PATROL_WEEKLY_DIGEST.md Email the Patrol weekly summary as a report schedule kind 2026-09-02 11:15:22 +01:00
PBS.md
PRIVACY.md Make telemetry consent a setup choice and retire the payload banner 2026-09-02 19:04:54 +01:00
PRODUCTION_SECURITY.md Contain agent command authority 2026-08-29 22:12:41 +01:00
PROXY_AUTH.md
PULSE_PRO.md Clarify Community OIDC role mapping 2026-08-26 02:31:52 +01:00
RBAC.md Enforce explicit SSO administrator grants 2026-08-31 00:43:42 +01:00
README.md docs: explain release channels and qualification 2026-09-08 12:51:15 +01:00
RECOVERY.md
RELAY.md
RELEASE_NOTES.md Prepare v6.4.3-rc.1 release 2026-09-01 21:37:41 +01:00
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 Point security disclosures at security@pulserelay.pro 2026-09-01 15:21:23 +01:00
STORAGE_ARCHITECTURE.md
TEMPERATURE_MONITORING.md
TROUBLESHOOTING.md docs: explain Proxmox package-update privilege boundary 2026-09-09 00:11:15 +01:00
TRUENAS.md Align TrueNAS guidance with JSON-RPC runtime 2026-09-01 18:32:39 +01:00
UNIFIED_AGENT.md Document per-node agent installs for PVE clusters 2026-09-01 06:36:02 +01:00
UNIFIED_RESOURCES.md
UPGRADE_v5.md
UPGRADE_v6.md Prepare v6.4.3-rc.1 release 2026-09-01 21:37:41 +01:00
VM_DISK_MONITORING.md
WEBHOOKS.md Expose stable webhook message keys 2026-08-26 12:04:43 +01:00
ZFS_MONITORING.md

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.