Monitoring Your OpenClaw Instance

Monitoring Overview

Keeping your OpenClaw instance healthy requires monitoring three things: gateway status, channel connections, and resource usage.

Gateway Status

CLI Check

openclaw status

Output shows:

• Gateway running/stopped
• Connected channels and their status
• Uptime
• Message count (today / total)
• Current model

Health Endpoint

If the web interface is enabled, check:

GET http://localhost:3000/health

Returns JSON with gateway health information.

Logging

Log Levels

{
  "logging": {
    "level": "info",
    "file": "~/.openclaw/logs/openclaw.log",
    "max_size": "10m",
    "max_files": 5
  }
}

Levels: debug, info, warn, error

Viewing Logs

# Follow logs in real time
tail -f ~/.openclaw/logs/openclaw.log

# With systemd
journalctl -u openclaw -f

# With Docker
docker logs -f openclaw

What's Logged

• Channel connection/disconnection events
• Message received/sent (without content by default)
• Tool executions
• Errors and warnings
• API call metrics (latency, tokens used)

Health Checks

External Monitoring

Set up uptime monitoring using:

• UptimeRobot — Free tier monitors the health endpoint
• Pingdom — More advanced monitoring
• GCP Uptime Checks — If hosted on Google Cloud

Internal Checks

OpenClaw runs internal health checks every 60 seconds:

• Channel connection status
• Memory usage
• Disk space
• API key validity

Alerting

Channel Disconnection

Get notified when a channel drops:

{
  "hooks": {
    "on_channel_disconnect": "curl -X POST https://your-webhook.com/alert -d '{"msg": "Channel disconnected"}'"
  }
}

Error Alerts

Send alerts on errors:

{
  "hooks": {
    "on_error": "notify-send 'OpenClaw Error' 'Check logs for details'"
  }
}

Claw for All Monitoring

Claw for All includes built-in monitoring:

• Dashboard shows VM status, uptime, and health
• Automatic restart on failures
• Email alerts for critical issues
• Resource usage graphs