17d56d0e01
Clean break, no compatibility alias. Renames the product name, the CLI binary (`ccam` -> `agenthub`), the env var prefix (`CCAM_` -> `AGENTHUB_`), the Prometheus metric namespace (`ccam_*` -> `agenthub_*`), the tmux session prefix (`ccam-lane-<id>` -> `agenthub-lane-<id>`), the per-repo runtime profile directory (`.ccam/profile` -> `.agenthub/profile`), the lanes state root (`~/.claude/ccam-lanes` -> `~/.claude/agenthub-lanes`), the bundled plugins (`plugins/ccam*` -> `plugins/agenthub*`) and their slash commands (`/ccam-doctor` -> `/agenthub-doctor`, `/ccam:*` -> `/agenthub:*`). Because there is no alias, an existing install has to be updated by hand: rename its `.ccam/profile` directory and any `CCAM_*` variables, and reinstall the plugin under its new name. Two other name families are deliberately left alone here, since they are not just strings: the `Claude-Code-Monitor` repository/marketplace name, and the `agent-dashboard` npm package plus its `~/.claude/agent-dashboard` runtime directory, which holds the live database and needs a migration rather than a rename. Verified: server 1406/1406, client 459/459, `grep -i ccam` clean across tracked files, `openapi.yaml` regenerated (95 paths, unchanged count).
3.1 KiB
3.1 KiB
description
| description |
|---|
| Run comprehensive health checks on the AgentHub system. Validates dashboard API, database, WebSocket, hooks, and disk usage. Use to verify the monitoring setup is working correctly. |
Health Check
Run a comprehensive health check on the Agent Monitor system.
Input
The user provides: $ARGUMENTS
This may be:
- "full" or empty (default: run all checks)
- "quick" for a fast connectivity check
- "deep" for extended checks including database integrity
Procedure
Run health checks in this order:
1. API Health
curl -sf http://localhost:4820/api/health
- Verify HTTP 200 response
- Check response time (<500ms expected, <1000ms acceptable)
- Confirm JSON response body
2. Database Health
curl -sf http://localhost:4820/api/stats
- Verify stats endpoint returns valid data
- Check that counts are non-negative integers
- Verify database file exists and has reasonable size
3. WebSocket Health
- Check that the WebSocket server is listening
- Verify WebSocket upgrade is supported on the dashboard port
4. API Endpoint Validation
Test each major endpoint:
curl -sf http://localhost:4820/api/sessions?limit=1
curl -sf http://localhost:4820/api/events?limit=1
curl -sf http://localhost:4820/api/analytics
curl -sf http://localhost:4820/api/pricing
curl -sf http://localhost:4820/api/settings/info
5. Hook Integration
- Verify hook handler script exists
- Check hooks are configured in
~/.claude/settings.json - Verify the handler script targets the correct dashboard URL
6. Disk & Resource Usage (deep mode only)
- Database file size
- Log file sizes (if any)
- Available disk space
- Node.js process memory usage (if accessible)
7. Data Freshness
- Time since last event ingested
- Time since last session created
- Check for stale active sessions (active but no events in >1 hour)
Output Format
Present as a system health dashboard:
╔══════════════════════════════════════════════╗
║ AGENT MONITOR HEALTH CHECK ║
║ Timestamp: 2025-04-11 12:00:00 UTC ║
╠══════════════════════════════════════════════╣
║ ║
║ API Server ............ ✅ OK (45ms) ║
║ Database .............. ✅ OK (2.4 MB) ║
║ WebSocket ............. ✅ OK ║
║ API Endpoints ......... ✅ 6/6 passing ║
║ Hook Integration ...... ⚠️ 5/7 hooks ║
║ Data Freshness ........ ✅ 3m ago ║
║ ║
║ Overall: HEALTHY (5/6 checks passed) ║
║ ║
╚══════════════════════════════════════════════╝
For any non-passing check, include detailed explanation and remediation steps below the dashboard.