"id": "sat-nyc-01", "ip": "192.168.1.10", "status": "active"
"satellites": [ "id": "sat-01", "ip": "10.0.0.2", "role": "cache", "status": "active", "id": "sat-02", "ip": "10.0.0.3", "role": "stream", "status": "degraded", "id": "sat-03", "ip": "10.0.0.4", "role": "log", "status": "offline" ] orca server satellite list
"id": "sat-lon-01", "ip": "10.2.0.5", "status": "offline" "id": "sat-nyc-01", "ip": "192
SELECT host, port, lag_bytes FROM satellite_replicas WHERE master_id = 'orca-01'; Some RPA platforms have an Orchestrator (Orca) server and satellites (robots running on VMs). The satellite list tracks which robots are available, their last heartbeat, and assigned jobs. 3. Typical Format of a “Satellite List” on an Orca Server Whether stored in a file, database, or in-memory structure, a satellite list usually includes: Typical Format of a “Satellite List” on an
curl -s http://orca-server.internal:8080/satellites | jq '.satellites[] | id, ip, status' Sample output:
Example query to get satellite list:
"id": "sat-nyc-02", "ip": "192.168.1.11", "status": "active"
