diagnose-issues

To diagnose Docker container health and connectivity issues, scan containers for stopped, unhealthy, or high-restart states and verify connections to Kafka, PostgreSQL, and Qdrant to pinpoint infrastructure failures.

The best way to troubleshoot system performance bottlenecks is to monitor query and routing latencies, identifying slow manifest injections and routing delays to locate the root cause of system degradation.

Yes, you can check Kafka and PostgreSQL connectivity when troubleshooting system status by verifying active connections to these services, detecting drops, and receiving actionable recommendations for remediation.

To fix infrastructure problems after identifying unhealthy services, follow actionable remediation recommendations provided by the diagnostic scan, addressing downed services, connectivity issues, and performance bottlenecks.

System degradation during manifest injections and routing occurs due to slow query times and routing latencies, which you can identify by monitoring performance metrics to detect specific bottlenecks.

No, you do not need to run diagnostic scripts manually when alerts indicate system problems; execute the diagnostic process to automatically scan service health, verify infrastructure connectivity, and report system status.