[ Switch to styled version → ]
beginner · 3 agents · 9 skills
Deploy a status page pipeline with 3 agents that automate service monitoring, status aggregation, and public incident communication. Each agent handles one stage of the pipeline, turning endpoint health checks into a live public status page with incident notifications for subscribers.
clawhub install pilot-status-page-setuppilot-healthpilot-cronpilot-metricspilot-event-filterpilot-datasetpilot-audit-logpilot-webhook-bridgepilot-announcepilot-slack-bridge<your-prefix>-monitor - Service Monitorpilot-health , pilot-cron , pilot-metrics<your-prefix>-aggregator - Status Aggregatorpilot-event-filter , pilot-dataset , pilot-audit-log<your-prefix>-publisher - Status Publisherpilot-webhook-bridge , pilot-announce , pilot-slack-bridge<your-prefix>-monitor → <your-prefix>-aggregator:1002 - health-check events<your-prefix>-aggregator → <your-prefix>-publisher:1002 - status-update events<your-prefix>-publisher → external:443 - incident-notification via webhook# Replace <your-prefix> with a unique name for your deployment (e.g. acme)
# On server 1 (service monitor)
clawhub install pilot-health pilot-cron pilot-metrics
pilotctl set-hostname <your-prefix>-monitor
# On server 2 (status aggregator)
clawhub install pilot-event-filter pilot-dataset pilot-audit-log
pilotctl set-hostname <your-prefix>-aggregator
# On server 3 (status publisher)
clawhub install pilot-webhook-bridge pilot-announce pilot-slack-bridge
pilotctl set-hostname <your-prefix>-publisher
# monitor <-> aggregator
# On monitor:
pilotctl handshake <your-prefix>-aggregator "setup: status-page"
# On aggregator:
pilotctl handshake <your-prefix>-monitor "setup: status-page"
# aggregator <-> publisher
# On aggregator:
pilotctl handshake <your-prefix>-publisher "setup: status-page"
# On publisher:
pilotctl handshake <your-prefix>-aggregator "setup: status-page"
pilotctl trust