Skip to content

Central IB Health Monitoring Dashboard

Overview

The Central IB Health Monitoring Dashboard provides a comprehensive view of the status of key Interactive Brokers (IB) services and Docker containers on Strato Servers. It enables to monitor the health of live and paper trading services, manage Docker containers.

Dashboard Sections

1. Server Health Status

Displays the real-time status of the following components:

  • Load Balancer: Indicates the health and connection status of the load balancer. Will route accordingly to live services.
  • Server 1 (232): Displays the health, live connection, and paper connection status for the first server.
  • Server 2 (227): Displays the same details for the second server.

Status Indicators

  • Healthy: Indicates the component is functioning properly.
  • Live Connected: Shows if live account is connected.
  • Paper Connected: Shows if paper account is connected.

2. Docker Container Management

Lists all Docker containers running on each server, along with descriptions and actions available:

Server 1 (232) Containers

  • algo-trader-live-ib-gateway-1: IB Gateway Live Trading Account 1
  • ib-p-haproxy-1.0: Load Balancer
  • ib-p-web_service_1-2.0: IB Web Service
  • ib-p-data_service_primary-2.0: IB Data Service
  • ib-test-restart-container: Testing Only

Server 2 (227) Containers

  • algo-trader-paper-ib-gateway-1: IB Gateway Paper Trading
  • algo-trader-live-acc-2-ib-gateway-1: IB Gateway Live Trading Account 2
  • ib-p-web_service_1-2.0: IB Web Service
  • ib-p-data_service_primary-2.0: IB Data Service

3. WebSocket Status

Indicates the connection status of the Load Balancer via WebSocket. Status examples: - Connection Successful - Connection Failed

Troubleshooting and Actions

Scenario 1: Live Service Not Healthy/Load Balancer Unreachable(Both live services are down)

  1. Restart the IB Gateway Live Trading Container:
  2. Example: Restart algo-trader-live-ib-gateway-1 (Server 1) or algo-trader-live-acc-2-ib-gateway-1 (Server 2).
  3. If the issue persists:
  4. Restart both the Web Service and Data Service for the affected server:
    • Web Service: ib-p-web_service_1-2.0
    • Data Service: ib-p-data_service_primary-2.0

Scenario 2: Paper Service Not Connected

  1. Restart the IB Gateway Paper Trading Container:
  2. Example: Restart algo-trader-paper-ib-gateway-1 (Server 2).
  3. If the issue persists:
  4. Restart both the Web Service and Data Service for the affected server:
    • Web Service: ib-p-web_service_1-2.0
    • Data Service: ib-p-data_service_primary-2.0

Notes

  • Wait for 5 mins to verify the status after restarting the container.
  • Monitor the WebSocket Status to confirm the connection is successful after troubleshooting.