How can I make sure the new Autoscaled Azure App Service instance is warm before it processes traffic?

Question

When autoload is enabled in the application service, Azure will add instances as necessary based on established rules. I always start with at least two copies. I would like to make sure that traffic is not directed to an instance of a new application until the application code is fully initialized. How can i do this? Can I add a timeout? Or is it done somehow automatically?

Answer 1

How can i do this? Can I add a timeout? Or is it done somehow automatically?

, , , , .

Azure , . .

, azure, .

---

"Azure " - , , - ? , , URL- 200 OK 2 .

, - 2, - , azure - .

, :

webserver web.config :

<tracing>  
  <traceFailedRequests>  
    <clear/>  
    <add path="*">  
      <traceAreas>  
      <add provider="WWW Server" areas="Authentication,Security,Filter,StaticFile,CGI,Compression,Cache,RequestNotifications,Module,Rewrite,iisnode" verbosity="Verbose" />  
      </traceAreas>  
      <failureDefinitions statusCodes="200-600" />  
    </add>  
  </traceFailedRequests>  
</tracing> 

, 2 , -. , . Azure - .

, :

:

fr00030.xml( , 5860 ):

fr00031.xml( , 8164 4015 )

, , ( ), .

, -.

Answer 2

web.config .

- :

<system.webServer>  
  <applicationInitialization >  
    <add initializationPage="/page-you-want-to-warm-up.php" hostName="your-app.azurewebsites.net"/> 
  </applicationInitialization>  
<system.webServer> 

, , , ( ) , , ..... ApplicationInitialization .

: http://ruslany.net/2015/09/how-to-warm-up-azure-web-app-during-deployment-slots-swap/

, , .