| « PreviousNext » | |
  | Did this page help you? Yes | No | Tell us about it... |
HealthCheck
Description
The HealthCheck data type.
Contents
- HealthyThreshold
Specifies the number of consecutive health probe successes required before moving the instance to the Healthy state.
Type: Integer
Required: Yes
- Interval
Specifies the approximate interval, in seconds, between health checks of an individual instance.
Type: Integer
Required: Yes
- Target
Specifies the instance being checked. The protocol is either TCP, HTTP, HTTPS, or SSL. The range of valid ports is one (1) through 65535.
Note
TCP is the default, specified as a TCP: port pair, for example "TCP:5000". In this case a healthcheck simply attempts to open a TCP connection to the instance on the specified port. Failure to connect within the configured timeout is considered unhealthy.
SSL is also specified as SSL: port pair, for example, SSL:5000.
For HTTP or HTTPS protocol, the situation is different. You have to include a ping path in the string. HTTP is specified as a HTTP:port;/;PathToPing; grouping, for example "HTTP:80/weather/us/wa/seattle". In this case, a HTTP GET request is issued to the instance on the given port and path. Any answer other than "200 OK" within the timeout period is considered unhealthy.
The total length of the HTTP ping target needs to be 1024 16-bit Unicode characters or less.
Type: String
Required: Yes
- Timeout
Specifies the amount of time, in seconds, during which no response means a failed health probe.
Note
This value must be less than the Interval value.
Type: Integer
Required: Yes
- UnhealthyThreshold
Specifies the number of consecutive health probe failures required before moving the instance to the Unhealthy state.
Type: Integer
Required: Yes
