Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Downtime for updated images #145

Open
paynecodes opened this issue Apr 26, 2024 · 1 comment
Open

Downtime for updated images #145

paynecodes opened this issue Apr 26, 2024 · 1 comment

Comments

@paynecodes
Copy link

paynecodes commented Apr 26, 2024

We had some downtime in our App Service today that appears to have been caused by container images being deployed (based on timing of log messages and know downtime window).

Is downtime expected? I was under the impression that a new container should be deployed and accepting traffic before the old container is taken offline.

If this is expected / likely to continually reoccur:
What are the best strategies to mitigate and/or speed up deployment to improve long downtimes such as these (16 minutes in this case).

If this is not expected or likely to have been the issue:

What logging options and configuration changes are necessary to be able to get more from logs via Log Stream?

@paynecodes paynecodes changed the title Downtime Downtime for updated images Apr 26, 2024
@samrueby
Copy link

App Service indeed wait until that new container is running and ready for HTTP requests before they switch over to it. 16 minutes is quite a long time- that is unexpected. The container starts for me < 2 minutes.

I believe the best logging option would be to configure a 'diagnostic setting' for your app service. Perhaps App Service Console Logs, App Service Application Logs, App Service Platform logs. Send to log analytics.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants