mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-05-02 21:40:14 +00:00
Adds IncludeAllDeployments option to show all deployments, not just problem ones (where replicas don't match desired). This provides parity with the existing --kube-include-all-pods flag. - Add IncludeAllDeployments to kubernetesagent.Config - Add --kube-include-all-deployments flag and PULSE_KUBE_INCLUDE_ALL_DEPLOYMENTS env var - Update collectDeployments to respect the new flag - Add test for IncludeAllDeployments functionality - Update UNIFIED_AGENT.md documentation Addresses feedback from PR #855
1.4 KiB
1.4 KiB
📝 Sensor Proxy Log Forwarding
Deprecated in v5:
pulse-sensor-proxyis deprecated and not recommended for new deployments. Usepulse-agent --enable-proxmoxfor temperature monitoring. This document is retained for existing installations during the migration window.
Forward audit.log and proxy.log to a central SIEM via RELP + TLS.
🚀 Quick Start
Run the helper script with your collector details:
sudo REMOTE_HOST=logs.example.com \
REMOTE_PORT=6514 \
CERT_DIR=/etc/pulse/log-forwarding \
CA_CERT=/path/to/ca.crt \
CLIENT_CERT=/path/to/client.crt \
CLIENT_KEY=/path/to/client.key \
bash -c "$(curl -fsSL https://raw.githubusercontent.com/rcourtman/Pulse/main/scripts/setup-log-forwarding.sh)"
📋 What It Does
- Inputs: Watches
/var/log/pulse/sensor-proxy/{audit,proxy}.log. - Queue: Disk-backed queue (50k messages) for reliability.
- Output: RELP over TLS to
REMOTE_HOST. - Mirror: Local debug file at
/var/log/pulse/sensor-proxy/forwarding.log.
✅ Verification
- Check Status:
sudo systemctl status rsyslog - View Mirror:
tail -f /var/log/pulse/sensor-proxy/forwarding.log - Test: Restart proxy and check remote collector for
pulse.audittag.
🧹 Maintenance
- Disable: Remove
/etc/rsyslog.d/pulse-sensor-proxy.confand restart rsyslog. - Rotate Certs: Replace files in
CERT_DIRand restart rsyslog.