About this article

• Audience: Operators monitoring shadow-canary and shadow-secondary health
• Goal: Read fleet registry and MQTT telemetry to confirm devices are online and recording
• Type: How-to

Summary

Fleet status is not a static table in public docs—it is whatever your proxy and MQTT bus report right now. Use the registry endpoint and latest telemetry to confirm each shadow role is healthy before running soaks or video workflows.

Prerequisites

• Phantom proxy running at https://<phantom-proxy>:8788
• Shadows deployed with distinct roles (shadow-canary, shadow-secondary)

1. Read the fleet registry

curl -s https://<phantom-proxy>:8788/fleet/registry

Look for each shadow role, device label, and bus identifier. Missing entries mean deploy or MQTT wiring is incomplete.

2. Read latest MQTT telemetry

curl -s https://<phantom-proxy>:8788/fleet/mqtt/latest

Confirm each device shows recent telemetry, detection payloads where expected, and recent_chunks when recording is active.

3. Probe recording status (optional)

curl -s -X POST 'https://<phantom-proxy>:8788/tools/call?target=<device-ip>' \
  -H 'Content-Type: application/json' \
  -d '{"tool":"get_recording_status","arguments":{}}'

Verify: storage_health is not CRITICAL before long soaks. If CRITICAL, prune first (prune guide).

Next steps

• First operator tasks — contract + soak gate
• Monitoring — TAP and observability
• API quick reference — all proxy endpoints

Operator depth

Authoritative fleet maps, container IDs, and session chronology live in private operator handoff (not published).