[ Switch to styled version → ]
beginner · 3 agents · 6 skills
Deploy monitoring agents across your fleet that continuously check service health, aggregate metrics, and route alerts to Slack or PagerDuty. Each server runs its own monitor agent while a central hub filters noise and dispatches notifications.
clawhub install pilot-fleet-health-monitor-setup <your-prefix>-web-monitor - Web Server Monitor pilot-health, pilot-alert, pilot-metrics <your-prefix>-db-monitor - Database Monitor pilot-health, pilot-alert, pilot-metrics <your-prefix>-alert-hub - Alert Aggregator pilot-webhook-bridge, pilot-alert, pilot-event-filter, pilot-slack-bridge <your-prefix>-web-monitor → <your-prefix>-alert-hub:1002 - health-alert events<your-prefix>-db-monitor → <your-prefix>-alert-hub:1002 - health-alert events<your-prefix>-alert-hub → external:1002 - forwarded alerts via webhook/announce# Replace <your-prefix> with a unique name for your deployment (e.g. acme)
# On server 1 (web server)
clawhub install pilot-health pilot-alert pilot-metrics
pilotctl set-hostname <your-prefix>-web-monitor
# On server 2 (database)
clawhub install pilot-health pilot-alert pilot-metrics
pilotctl set-hostname <your-prefix>-db-monitor
# On server 3 (alert aggregator)
clawhub install pilot-webhook-bridge pilot-alert pilot-event-filter pilot-slack-bridge
pilotctl set-hostname <your-prefix>-alert-hub
# On alert-hub:
pilotctl handshake <your-prefix>-db-monitor "setup: fleet-health-monitor"
# On db-monitor:
pilotctl handshake <your-prefix>-alert-hub "setup: fleet-health-monitor"
# On alert-hub:
pilotctl handshake <your-prefix>-web-monitor "setup: fleet-health-monitor"
# On web-monitor:
pilotctl handshake <your-prefix>-alert-hub "setup: fleet-health-monitor"
pilotctl trust