# Monitor Server Connector Plan

## Current design

The plugin uses:

- **HTTP heartbeat** to `/monitor/server/heartbeat-v2`
- **API Key authentication** via `X-API-Key`
- **Gateway lifecycle hooks**: `gateway_start` / `gateway_stop`

## No longer used

The following design has been retired:

- challenge UUID
- RSA public key fetch
- encrypted handshake payload
- WebSocket telemetry

## Runtime flow

1. Gateway loads `harborforge-monitor`
2. Plugin reads config from OpenClaw plugin config
3. On `gateway_start`, plugin launches `server/telemetry.mjs`
4. Sidecar collects:
   - system metrics
   - OpenClaw version
   - plugin version
   - configured agents
5. Sidecar posts telemetry to backend with `X-API-Key`

## Payload

```json
{
  "identifier": "vps.t1",
  "openclaw_version": "OpenClaw 2026.3.13 (61d171a)",
  "plugin_version": "0.1.0",
  "agents": [],
  "cpu_pct": 10.5,
  "mem_pct": 52.1,
  "disk_pct": 81.0,
  "swap_pct": 0.0,
  "load_avg": [0.12, 0.09, 0.03],
  "uptime_seconds": 12345
}
```