A monitor issues health monitor requests at regular intervals to evaluate the health of each server within an origin pool.
When a pool becomes unhealthy, your load balancer takes that pool out of the server rotation.
Health monitor requests that result in a status change for an origin server are recorded as events in the Load Balancing event logs.
For an up-to-date list of monitor properties, refer to Monitor properties in our API documentation.
For step-by-step guidance, refer to Create monitors.
Health monitor regions
When you attach a monitor to a pool, you can select multiple regions to increase reporting accuracy.
For each option selected in a pool’s Health Monitor Regions, Cloudflare sends health monitor requests from three separate data centers in that region.
If the majority of data centers for that region pass the health monitor requests, that region is considered healthy. If the majority of regions is healthy, then the origin itself will be considered healthy.
All Data Centers (Enterprise only)
Health monitor probes are sent from every single data center in Cloudflare’s network to the origins within the associated pool. This allows probes to hit each origin during intervals set by the customer.
Three health monitor probes per region are sent to each origin in the associated pool. There are a total of 13 regions, resulting in 39 probes.
Three health monitor probes are sent from each specified region within the pool configuration.
Host header prioritization
When a load balancer runs health monitor requests, headers set on an origin override headers set on a monitor. For more details, refer to Override HTTP Host headers.
The Cloudflare API supports the following commands for monitors. Examples are given for user-level endpoint but apply to the account-level endpoint as well.
|Overwrite specific properties|
|Overwrite existing monitor|