deployment-diagnosis-agent

To troubleshoot an unhealthy container deployment, trace image, config, port, network, health-check, and environment mismatches to identify why the service is unreachable and narrow the failure to the smallest useful cause.

A service behaves differently in deployment than in development due to config, image, port, network, or environment mismatches introduced during the deployment process that alter runtime behavior.

The best way to diagnose runtime failures where a service fails to bind or returns bad responses is to trace health-check behavior and verify environment and network configurations to locate mismatches.

To find the root cause of a deployment failure, trace configuration and runtime mismatches to generate a structured diagnosis containing gathered evidence, a likely root cause, confidence level, and a recommended fix.

Yes, you can diagnose health-check and network mismatches without external dependencies by tracing the deployment configuration directly to verify behavior and identify mismatches causing the failure.