anchor.diff:  
   ### <a id="health_check_timeout"></a> Health Check Timeouts
   
  -The value configured for the health check timeout is the amount of time allowed to elapse between starting up an app and the first healthy response from the app. If the health check does not receive a healthy response within the configured timeout, then the app is declared unhealthy. 
  +The value configured for the health check timeout is the amount of time allowed to elapse between starting up an app and the first healthy response from the app. If the health check does not receive a healthy response within the configured timeout, then the app is declared unhealthy.
   
   <%=vars.app_healthcheck_timeout%>
   
  
positive.code: </tr>
  <tr>
  <td>can provide an <code>HTTP 200</code> response</td>
  <td><code>http</code>. The HTTP health check does a GET request to the configured HTTP endpoint. When the health check receives an <code>HTTP 200</code> reponse, the app is declared healthy. If possible, HTTP is the recommended health check mechanism. The advantage of using an HTTP health check is that a healthy HTTP response ensures that the web app is ready to serve HTTP requests. </td>
  </tr>
  <tr>
  <td>can receive TCP connections (including HTTP web applications)
  </td>
  <td>
  <code>port</code>. A port health check makes a TCP connection to the port or ports configured for the application. For applications with multiple ports, a health check monitors each port. If you do not specify a health check type for your application, then <code>port</code> is used.</code>
  </td>
  </tr>
  <tr>
  
negative.code: 	</tr>
  	<tr>
  		<td>3</td>
  		<td>Cloud Controller stages, starts, and runs the app.
  		</td>
  	</tr>
  	<tr>
  		<td>4</td>
  		<td>Based on the type specified for the app, Cloud Controller configures a health check that runs periodically for each application instance.
  		</td>
  	</tr>
  	<tr>
  		<td>5</td>
  		<td>When Diego starts an app instance, the application health check runs every 2 seconds until a response indicates that the app instance is healthy or until the health check timeout has elapsed.
  		</td>
  
  	</tr>
  	<tr>
  	   <td>6</td>
  		<td>When an app instance becomes healthy, its route is advertised, if applicable. Subsequent health checks are run every 30 seconds once the app becomes healthy.
  		</td>
          </tr>
  	<tr>
  		<td>7</td>
  		<td>If a previously healthy app instance fails a health check, Diego then considers that particular instance to be unhealthy. As a result, Diego tears down the instance, and then reschedules it. The teardown of the app instance is reported back to the Cloud Controller as a crash event. When an app instance crashes, Diego immediately attempts to restart the app instance several times. If the app instance continues to crash, then an exponential back off is applied to the restart attempts.</td>
  	</tr>
  </table>
  
  