Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Load Balancing] Update dynamic-steering.mdx #19053

Merged
merged 2 commits into from
Jan 10, 2025
Merged

[Load Balancing] Update dynamic-steering.mdx #19053

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c1f30b5
Update dynamic-steering.mdx
ngayerie Jan 7, 2025
415c73c
Apply suggestions from code review
angelampcosta Jan 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions ...ncing/understand-basics/traffic-steering/steering-policies/dynamic-steering.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,3 +22,10 @@ For TCP health monitors, calculated latency may not reflect the true latency to
The diagram below shows how Cloudflare would route traffic to the pool with the lowest EWMA among three regions: Eastern North America, Europe, and Australia. In this case, the ENAM pool is selected because it has the lowest RTT.

![Dynamic steering routes traffic to the fastest available pool](~/assets/images/load-balancing/traffic-steering-2.png)

:::note

In order to get dynamic steering to work as expected, the [Health Monitor Region](/load-balancing/monitors/#health-monitor-regions) need to be set to **All Regions**.
angelampcosta marked this conversation as resolved.
Show resolved Hide resolved
The Enterprise-only **All Data Centers** option can also work.
angelampcosta marked this conversation as resolved.
Show resolved Hide resolved

:::
Loading