导航|地址|刷新
Create monitor
图
Skip to contentDocumentation Index
Fetch the complete documentation index at: https://developers.cloudflare.com/learning-paths/llms.txt
Use this file to discover all available pages before exploring further.



DocsDirectoryAPISDKsChangelog

Search

Log in






Load balancing (Learning Paths)

/





Concepts


Overview

What is load balancing?

Components of a load balancer

Monitors and health checks

Routing traffic






Planning your load balancer


Overview

Types of load balancers

Session affinity

Endpoint steering policies

Server and pool health

Traffic steering

Custom load balancing rules

Account-level load balancing






Setup


Overview

Hostname preparation

Create monitor

Create pools

Check pool health

Create load balancer on test domain

Send traffic and review analytics

Route production traffic

Next steps






Agent resources


Agent setup ↗

Cloudflare Skills ↗

Code Mode MCP Server ↗

Domain-specific MCP Servers ↗MCP

Learning Paths llms.txt ↗

Learning Paths llms-full.txt ↗

Cloudflare Docs llms.txt ↗

Cloudflare Docs llms-full.txt ↗













Home

/Learning Paths

/…
Load Balancing


/Setup

/Create monitor



Create monitor


Last updated Apr 23, 2026|Copy as Markdown|View as Markdown|Agent setup




Instead of starting on your production domain, you likely should create a load balancer on a test or staging domain. This may involve temporary changes to your monitors and pools, depending on your infrastructure setup.

Starting with a test domain allows you to verify everything is working correctly before routing production traffic.





Set up the monitor
You can create a monitor within the load balancer workflow or in the Monitors tab:


Go to Load Balancing.



Select the Monitors tab.



Select Create monitor.



Add the following information:
Type: The protocol to use for health monitors
Non-enterprise customers: Choose HTTP, HTTPS, or TCP.

Enterprise customers: Choose HTTP, HTTPS, TCP, UDP ICMP, ICMP Ping, or SMTP.


Path: The endpoint path to run health monitor requests against

Port: The destination port for health monitors




For additional settings, select Advanced health monitor settings:
Interval:
By increasing the default, you can improve failover time, but you may also increase load on your endpoints.

Minimum time in seconds is 60 (Pro), 15 (Business), and 10 (Enterprise).


Timeout and Retries:
The health monitor request will return unhealthy if it exceeds the duration specified in Timeout (and exceeds this duration more times than the specified number of Retries).


Expected Code(s): The expected HTTP response codes listed individually (200, 302) or as a range (for example, entering 2xx would cover all response codes in the 200 range).

Response Body:
Looks for a case-insensitive substring in the response body.

Make sure that the value is relatively static and within the first 10 KB of the HTML page.


Simulate Zone:
It is recommended to use the same zone in which the Load Balancer exists.

Changes the egress zone settings of a health monitor request to ensure compatibility with features like Authenticated Origin Pulls (mTLS), Argo Smart Routing, Bring your own CA (mTLS), Dedicated CDN Egress IPs, and HTTP/2 to Origin.


Follow Redirects:
Instead of reporting a 301 or 302 code as unhealthy, the health monitor request follows redirects to the final endpoint.


Configure Request Header(s):
Useful if your endpoints are expecting specific incoming headers.


Header:
The HTTP request headers to send in the health monitor. It is recommended that you set a Host header by default. The User-Agent header cannot be overridden. This parameter is only valid for HTTP and HTTPS monitors.





Select Save.



Note


To increase confidence in pool status, you can also increase the consecutive_up and consecutive_down fields when creating a monitor with the API.

To become healthy or unhealthy, monitored endpoints must pass this health monitor request the consecutive number of times specified in these parameters.


Prepare your servers
Make sure that your firewall or web server does not block or rate limit your configured health monitors or requests associated with Cloudflare IP addresses ↗.

Each health monitor has the HTTP user-agent of "Mozilla/5.0 (compatible; Cloudflare-Traffic-Manager/1.0; +https://www.cloudflare.com/traffic-manager/; pool-id: $poolid)", where the $poolid is the first 16 characters of the associated pool.


Caution


If you know that your endpoint is healthy but Load Balancing is reporting it as unhealthy, refer to our Monitor troubleshooting guide.




Set up the monitor
For a full list of monitor properties, refer to Create Monitor. If you need help with API authentication, refer to Cloudflare API documentation.

Required API token permissions
At least one of the following token permissions is required:
Load Balancing: Monitors and Pools Write
Create Monitorbashcurl "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/load_balancers/monitors" \ --request POST \ --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \ --json '{ "type": "https", "description": "Login page monitor", "method": "GET", "path": "/health", "header": { "Host": [ "example.com" ], "X-App-ID": [ "abc123" ] }, "port": 8080, "timeout": 3, "retries": 0, "interval": 90, "expected_body": "alive", "expected_codes": "2xx", "follow_redirects": true, "allow_insecure": true, "consecutive_up": 3, "consecutive_down": 2, "probe_zone": "example.com" }'
The response contains the complete definition of the new monitor.
Responsejson{ "success": true, "errors": [], "messages": [], "result": { "id": ":monitor-id", "created_on": "2021-01-01T05:20:00.12345Z", "modified_on": "2021-01-01T05:20:00.12345Z", "type": "https", "description": "Login page monitor", "method": "GET", "path": "/health", "header": { "Host": [ "example.com" ], "X-App-ID": [ "abc123" ] }, "port": 8080, "timeout": 3, "retries": 0, "interval": 90, "expected_body": "alive", "expected_codes": "2xx", "follow_redirects": true, "allow_insecure": true, "consecutive_up": 3, "consecutive_down": 2, "probe_zone": "example.com" }}Prepare your servers
Make sure that your firewall or web server does not block or rate limit your configured health monitors or requests associated with Cloudflare IP addresses ↗.

Each health monitor has the HTTP user-agent of "Mozilla/5.0 (compatible; Cloudflare-Traffic-Manager/1.0; +https://www.cloudflare.com/traffic-manager/; pool-id: $poolid)", where the $poolid is the first 16 characters of the associated pool.


Caution


If you know that your endpoint is healthy but Load Balancing is reporting it as unhealthy, refer to our Monitor troubleshooting guide.






Example monitor configuration


FieldValue
TypeHTTP
Path/
Port80
Interval60
MethodGET
Timeout5 seconds
Retries2
Expected Code(s)200




PreviousHostname preparationNextCreate pools


Was this helpful?

YesNo

Edit pageReport issue




On this page

Overview


Edit pageReport issue














Getting started
PlansContact salesPartnersFind a partnerStartupsUnder attack?Domain name search


Company
AboutCareersInvestorsPressPress kitGlobal network




Public interest
Project GalileoAthenian ProjectCloudflare for CampaignsProject FairshotImpact/ESG


Compliance
Compliance resourcesTrust HubData ProtectionResponsible AITransparency reportReport abuse




Resources
App innovation reportCloudflare RadarCase studiesStatusSupportEventsBlog


Developers
DocumentationLearning centerCommunity




Solutions
SSE and SASE platformCloudflare AI CloudAI SecurityFrontend Development PlatformMulti-Tenant Platform DevelopmentWeb Security Platform


Start BuildingLog In












© 2026 Cloudflare, Inc.

Privacy policy|Report security issues|Terms of use|Trademark
|
Your privacy choices








Docs




------
导航页 打开网址