Thanks for asking question! You can access the diagnostic logs by accessing the console logs generated from inside the container.
First, turn on container logging by running the below command in the Azure Cloud Shell
az webapp log config --name <app-name> --resource-group myResourceGroup --docker-container-logging filesystem
You can now see the log stream by running below command.
az webapp log tail --name <app-name> --resource-group myResourceGroup
You may also investigate the log files from the browser link: https://<app-name>.scm.azurewebsites.net/api/logs/docker
To add to this:
- If the browser has timed out waiting for a response from App Service, this indicates that App Service started the Gunicorn server, but
the arguments that specify the app code are incorrect. - Check that your app is structured as App Service expects for Django or Flask, or use a custom startup command.
- try capturing a network trace to help identify if responses from the endpoint are slower than expected.
- If high number of processes are waiting for CPU consider scaling up to a higher SKU.
You may refer to this official doc link: https://learn.microsoft.com/en-us/azure/app-service/configure-language-python
Let me know if issue persists.