Healthchecks are used to customize the way Fastly checks on your Backends. If an origin server is marked unhealthy due to health checks, Fastly will stop attempting to send requests to it. If all origin servers are marked unhealthy, Fastly will attempt to serve stale. If no stale object is available, a 503 will be returned to the client.
|Integer||How often to run the healthcheck in milliseconds.|
|Integer||The status code expected from the host.|
|String||Which host to check.|
|Integer||Whether to use version 1.0 or 1.1 HTTP.|
|Integer||When loading a config, the initial number of probes to be seen as OK.|
|String||Which HTTP method to use.|
|String||The name of the healthcheck.|
|String||The path to check.|
|String||The alphanumeric string identifying a service.|
|Integer||How many healthchecks must succeed to be considered healthy.|
|Integer||Timeout in milliseconds.|
|Integer||The current version of a service.|
|Integer||The number of most recent healthcheck queries to keep for this healthcheck.|
User contributed notes
We welcome comments that add use cases, ideas, tips, and caveats. All comments will be moderated before publication. To post support questions, visit our support center and we'll find you the help you need.