tencent cloud

Tencent Cloud Smart Advisor

Release Notes
Product Introduction
Overview
Features
Product Strengths
Scenarios
Customer Cases
Purchase Guide
Getting Started
Using TSA to Perform a Cloud Risk Assessment
Using TSA to Execute a Chaos Experiment on CFG
Operation Guide
Operation Guide to TSA-Cloud Architecture
Operation Guide to TSA-Cloud Risk Assessment
Operation Guide to TSA-Chaotic Fault Generator
Operation Guide to TSA-Digital Assets
Permission Management
API Documentation
History
Introduction
API Category
Making API Requests
Other APIs
Task APIs
Cloud Architecture Console APIs
Data Types
Error Codes
FAQs
FAQs: TSA
FAQs: TSA-Cloud Risk Assessment
FAQs: TSA-Cloud Architecture
FAQs: TSA-Chaotic Fault Generator
Related Protocol
Tencent Cloud Smart Advisor Service Level Agreement
PRIVACY POLICY MODULE CHAOTIC FAULT GENERATOR
DATA PRIVACY AND SECURITY AGREEMENT MODULE CHAOTIC FAULT GENERATOR
Contact Us

Primary-Secondary Stream Switch

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2025-03-24 15:29:51
The primary-secondary stream switch fault scenario can simulate primary-secondary stream switch caused by stream push anomalies. By observing the post-fault behavior, you can verify whether downstream playback is normal after the primary-secondary stream switch and help evaluate the impact duration of primary-secondary switch on downstream playback.

Experiment Preparation

For CSS online streams, you can go to CSS > Stream Management > Online Streaming to view.
Note:
1. Primary-secondary stream switch will genuinely switch the primary-secondary streams. Please carefully evaluate the impact when conducting experiments in a production environment.
2. The primary-secondary stream switch fault is equivalent to manually operating the primary-secondary stream switch on the CSS console.
3. The primary-secondary stream switching fault requires the primary-secondary streams to have downstream playback, otherwise the switching will fail.

Experiment Steps

Step 1: Create an experiment

1. Log in to Tencent Cloud Smart Advisor > Chaotic Fault Generator, and follow the steps in Quick Start Guide to create an experiment. In the action group configuration, select Audio and Video for Instance Type, and CSS (Stream Push Domain Name) for Instance Object. Click Add Instance to add the push domain name corresponding to the experiment stream.
2. After adding the domain name, click Experiment Actions and then Add Now to add the experiment action. Select the Primary-secondary stream switch fault action and configure the action parameters, where the StreamName field is the stream you will inject the fault into (supporting up to 20 different streams for concurrent operations).
3. After confirmation, click Next to enter the Global Configuration page, select the Execution Method for the action, configure Guardrail Policy, and set up Monitoring Metrics.
Note:
Fault actions for CSS (stream push domain name) do not currently support configuring monitoring metrics.
4. Click Submit when it is completed, then click Experiment details. The system will automatically pre-check the resources you added to determine if they meet the experiment execution conditions (Pre-check does not execute the experiment actions).
Stream push disabled will perform the following verification. Ensure the environment passes the pre-check before starting the experiment, or it may fail. After issues are fixed, you can click Double-Check to initiate the pre-check again.
Pre-check items for the primary-secondary stream switch:
Check whether the selected domain name is enabled and is a stream push domain name.
Confirm whether the specified stream is an online stream.

Step 2: Execute the experiment

Click Execute on the action to start executing the fault action.

Step 3: Observe results

1. After performing primary-secondary stream switch, enter CSS Console > Stream Management, and click Primary-secondary Stream to observe the current status of the primary-secondary streams.
2. In CSS Console > Business Monitoring > Exception Events, click Primary-secondary Stream Events to view Proactive Switchover abnormal events.
3. After switching, you can simultaneously observe the changes in downstream playback, which typically switches within 1 to 3 seconds.
4. You can view the impact on Live Playback, User distribution, Top playbacks, and Origin Server via CSS > Business Monitoring > Operational Analysis. For details, see Operation Analysis.

Step 4: Fault Recovery

In the CFG platform, click Recover Action to switch back the primary-secondary streams. After successful execution, check if the items observed in Step 3 have been recovered.

도움말 및 지원

문제 해결에 도움이 되었나요?

피드백