tencent cloud

Tencent Cloud EdgeOne

Release Notes and Announcements
Release Notes
Security Announcement
Announcements
Product Introduction
Overview
Strengths
Use Cases
Comparison Between EdgeOne and CDN Products
Use Limits
Purchase Guide
Description of Trial Plan Experience Benefits
Free Plan Guide
Billing Overview
Billing Items
Subscriptions
Renewals
Instructions for overdue and refunds
Comparison of EdgeOne Plans
About "clean traffic" billing instructions
DDoS Protection Capacity Description
Getting Started
Choose business scenario
Quick access to website security acceleration
Quick deploying a website with Pages
Domain Service&Origin Configuration
Domain Service
HTTPS Certificate
Origin Configuration
Site Acceleration
Overview
Access Control
Smart Acceleration
Cache Configuration
File Optimization
Network Optimization
URL Rewrite
Modifying Header
Modify the response content
Rule Engine
Image&Video Processing
Speed limit for single connection download
DDoS & Web Protection
Overview
DDoS Protection
Web Protection
Bot Management
API Discovery(Beta)
Edge Functions
Overview
Getting Started
Operation Guide
Runtime APIs
Sample Functions
Best Practices
Pages
L4 Proxy
Overview
Creating an L4 Proxy Instance
Modifying an L4 Proxy Instance
Disabling or Deleting an L4 Proxy Instance
Batch Configuring Forwarding Rules
Obtaining Real Client IPs
Data Analysis&Log Service
Log Service
Data Analysis
Alarm Service
Site and Billing Management
Billing Management
Site Management
Version Management
General Policy
General Reference
Configuration Syntax
Request and Response Actions
Country/region and Corresponding Codes
Terraform
Overview
Installing and Configuring Terraform
Practical Tutorial
EdgeOne Skill User Guide
Automatic Warm-up/Cache Purge
Resource Abuse/hotlinking Protection Practical
HTTPS Related Practices
Acceleration Optimization
Scheduling Traffic
Data Analysis and Alerting
Log Platform Integration Practices
Configuring Origin Servers for Cloud Object Storage (Such As COS)
CORS Response Configuration
API Documentation
History
Introduction
API Category
Making API Requests
Site APIs
Acceleration Domain Management APIs
Site Acceleration Configuration APIs
Edge Function APIs
Alias Domain APIs
Security Configuration APIs
Layer 4 Application Proxy APIs
Content Management APIs
Data Analysis APIs
Log Service APIs
Billing APIs
Certificate APIs
Origin Protection APIs
Load Balancing APIs
Diagnostic Tool APIs
Custom Response Page APIs
API Security APIs
DNS Record APIs
Content Identifier APIs
Legacy APIs
Ownership APIs
Image and Video Processing APIs
Multi-Channel Security Gateway APIs
Version Management APIs
Data Types
Error Codes
FAQs
Product Features FAQs
DNS Record FAQs
Domain Configuration FAQs
Site Acceleration FAQs
Data and Log FAQs
Security Protection-related Queries
Origin Configuration FAQs
Troubleshooting
Reference for Abnormal Status Codes
Troubleshooting Guide for EdgeOne 4XX/5XX Status Codes
520/524 Status Code Troubleshooting Guide
521/522 Status Code Troubleshooting Guide
Tool Guide
Agreements
Service Level Agreement
Origin Protection Enablement Conditions of Use
TEO Policy
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary
DocumentationTencent Cloud EdgeOnePractical TutorialScheduling TrafficThrough traffic orchestration to multiple service providers

Through traffic orchestration to multiple service providers

PDF
Focus Mode
Font Size
Last updated: 2025-07-28 10:23:22
This article introduces how to use the traffic scheduling feature of EdgeOne Service to help you flexibly allocate the traffic of a domain name to multiple service providers for joint service, disperse risks and achieve high availability for business disaster recovery.




Document Target

This document is expected to take 10 minutes to learn. By studying this document, you can understand:
1. What is traffic scheduling management?
2. How to use traffic scheduling to distribute traffic to multiple service providers for joint service.
3. How to ensure high availability of services through traffic scheduling.

Background Introduction

Websites purchase security acceleration services to improve user access experience and business security, but do not want to schedule all traffic to one service provider. In case of failure, the impact is significant, and traffic needs to be flexibly allocated to multiple service providers for joint service to reduce risks and achieve high availability. The traditional solution is for users to use their own DNS service providers to perform complex configuration pointing for domain names, such as setting different service providers according to regions, operators, etc. The operation and management are relatively complex. EdgeOne provides traffic scheduling management tools, allowing users to allocate traffic according to countries, provinces, regions, operators, etc., and quickly change and switch services to ensure high availability of business disaster recovery.

Prerequisites

1. Add a site according to the Site Access Guide, purchase the EdgeOne Enterprise plan, and connect the site through CNAME.
2. Add the domain name that needs traffic scheduling switching in the EdgeOne console, and configure it according to the CNAME Access Mode Add Domain Name Guide.

Preset Scenarios

Assume that the domain name a.exampe.com currently uses CDN provider B for all traffic, and consider introducing other providers for joint scheduling. At the same time, when a certain provider encounters problems, traffic scheduling can be switched.
Overall scheduling strategy:
Switch Singapore users to use CDN provider B service.
Australian users use EdgeOne and CDN provider A for joint service, with EdgeOne accounting for 60% and CDN provider A accounting for 40%.
Other regions use the default scheduling and uniformly use EdgeOne service.

Operation Steps

Step 1: Select the domain name

1. Log in to the Tencent Cloud EdgeOne console, enter Service Overview in the left menu bar, and click the site to be configured under Website Security Acceleration.
2. After entering the site, click Domain Name Service > Traffic Scheduling Management in the menu bar to enter the Traffic Scheduling Management page, and click Add Scheduling Policy.



3. On the Traffic Scheduling Management page, click Add Scheduling Policy, select a.example.com, and click Create.




Step 2: Set the policy

1. Add service providers. In this scenario, because it is a multi-provider joint service, the default EdgeOne scheduling CNAME is available, and the CNAME domain names of CDN provider A and CDN provider B can be added separately.



2. Add policy submission configuration, add two policies, and add Chinese mainland and Singapore regions in Line/Region respectively:
Singapore: Select CDN provider B as the service provider.
Australia: Click Add a Service in the service provider section, and select EdgeOne and CDN provider A respectively, with EdgeOne setting a weight of 60 and CDN provider A setting a weight of 40.
Default: By default, others use EdgeOne service.




Step 3: Switch resolution

1. After submitting the policy configuration, return to the Traffic Scheduling Management list page. EdgeOne will assign a traffic scheduling CNAME to the domain name, which is consistent with the default CNAME of the domain name.
2. If the domain name resolution has been switched to EdgeOne, no change is required, and the current network policy takes effect immediately. If the domain name resolution has not been switched, you need to go to your DNS service provider to complete the CNAME configuration before the traffic scheduling policy can take effect.

Step 4: Verify Effectiveness

1. DNS resolution effectiveness check

You can use the nslookup or dig command to check the current domain name resolution effectiveness status.
Windows
Mac or Linux
In the Windows system, open the cmd running program, take the domain name a.example.com as an example, and judge the effectiveness of the Chinese mainland region. You can run in cmd: nslookup -qt=cname a.example.com, and check the CNAME information of the domain name according to the running resolution result. If the CNAME assigned by EdgeOne appears, the traffic switch is successful.



You can use the dig command to verify, take the domain name a.example.com as an example, you can run the command in the terminal: dig a.example.com, and check the CNAME information of the domain name according to the running resolution result. If the CNAME assigned by EdgeOne appears, the traffic switch is successful.





2. Traffic statistics change

Take Singapore as an example, enter the traffic analysis page of site a.example.com's data analysis, add a filter condition host equals a.example.com, and check the traffic trend curve change.
For example: The current Singapore bandwidth is 100Mpbs. When Singapore switches to EdgeOne, the bandwidth curve of the EdgeOne console will increase to 100Mbps bandwidth.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback