Provider Logs
Public guide to reading Provider startup logs without exposing private runtime configuration.
What Logs Should Tell You
Provider logs should make startup state clear without leaking secrets. A healthy startup normally confirms configuration loading, dependency connectivity, exchange connector readiness, REST availability, WebSocket availability, and health status.
Safe Checks
- Confirm the Provider process started and did not restart repeatedly.
- Confirm health checks pass before connecting Studio.
- Confirm exchange connectors initialize without printing full credentials.
- Confirm REST and WebSocket surfaces are available through the Provider gateway.
- Check that warnings do not expose tokens, private keys, or account secrets.
Where To Troubleshoot
Use public docs for the high-level flow and the owning Provider repository for exact log labels, environment names, and local commands. Internal Redis, database, queue, and downstream service details should remain in private repository documentation.
For current local diagnostics, use trading.apps/docs/ai/local-provider-stack-runbook.md.