api-check

You can check the health and status of trading platform services by verifying API endpoints and Docker containers. This process reports operational status, response times, memory usage, and version information for backend services like Redis and PostgreSQL.

Monitoring Docker container status alongside backend APIs requires direct access to service endpoints and Docker commands. This approach provides comprehensive verification, optionally displaying container status while checking API, UI, ML Server, and Executor services.

Yes, detailed status reporting with response times and memory usage is supported. By running a health check against your infrastructure components, you receive verbose output including memory metrics, response latency, and version information for services like Redis and PostgreSQL.

Service health monitoring works with Redis and PostgreSQL databases by directly accessing their endpoints. It verifies their accessibility and operational status, ensuring critical infrastructure components within the trading platform are running as expected before a session.

To verify backend service accessibility before starting a trading session, run a comprehensive health check. This confirms API, UI, ML Server, Executor, and Risk services are healthy by directly querying their endpoints and checking Docker container statuses.

Direct endpoint access is required for infrastructure health checks to accurately query service status and retrieve metrics like response times. Without direct network access to endpoints and Docker commands, comprehensive verification of trading platform components is not possible.