Files
Pulse/docs
rcourtman 8c4bef27f0 docs: improve reverse proxy HTTPS detection and Swarm troubleshooting
- Add detailed HTTPS detection troubleshooting to REVERSE_PROXY.md
- Explain X-Forwarded-Proto header requirement for nginx/Caddy/Apache
- Add Docker Swarm troubleshooting section to UNIFIED_AGENT.md
- Document how to force Docker runtime if auto-detection fails

Based on customer feedback.
2026-01-07 18:23:48 +00:00
..

📚 Pulse Documentation

Welcome to the Pulse documentation portal. Here you'll find everything you need to install, configure, and master Pulse.


🚀 Getting Started

  • Installation Guide Step-by-step guides for Docker, Kubernetes, and bare metal.
  • Configuration
    Learn how to configure authentication, notifications (Email, Discord, etc.), and system settings.
  • Deployment Models
    Where config lives, how updates work, and what differs per deployment.
  • Migration Guide
    Moving to a new server? Here's how to export and import your data safely.
  • Upgrade to v5
    Practical upgrade guidance and post-upgrade checks.
  • FAQ
    Common questions and quick answers.

🛠️ Deployment & Operations

🔐 Security

  • Security Policy The core security model (Encryption, Auth, API Scopes).
  • Proxy Auth Authentik/Authelia/Cloudflare proxy authentication configuration.

New in 5.0

  • Pulse AI Optional assistant for chat, patrol findings, alert analysis, and execution workflows.
  • Metrics History Persistent metrics storage with configurable retention.
  • Mail Gateway Proxmox Mail Gateway (PMG) monitoring.
  • Auto Updates One-click updates for supported deployments.
  • Kubernetes Helm deployment (ingress, persistence, HA patterns).

🚀 Pulse Pro

Pulse Pro unlocks LLM-backed AI Patrol — automated background monitoring that spots issues before they become incidents.

  • Learn more at pulserelay.pro
  • AI Patrol deep dive
  • Pulse Pro technical overview
  • What you actually get: LLM-backed patrol analysis, alert-triggered deep dives, Kubernetes AI analysis, and optional auto-fix workflows.
  • Technical highlights: correlation across nodes/VMs/backups/containers, trend-based capacity predictions, and findings you can resolve/suppress.
  • Scheduling: 10 minutes to 7 days (default 6 hours).

📡 Monitoring & Agents

💻 Development


Found a bug or have a suggestion?

GitHub Issues