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 Single Path Interruption

PDF
フォーカスモード
フォントサイズ
最終更新日: 2025-03-24 15:29:52
Primary-secondary stream single path interruption simulates the scenario where the primary stream is interrupted unexpectedly in the primary-secondary stream push scenario. By observing the post-fault behavior, you can verify whether the secondary stream can be switched normally and the impact 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 single path interruption will genuinely disconnect one of the streams in the primary-secondary stream line. Please carefully evaluate the impact when conducting experiments in a production environment.
2. Stream push disabled is equivalent to manually operating primary-secondary stream single path disconnection on the CSS console.
3. Primary-secondary stream single path interruption does not have a recovery action and requires the client to actively recover stream push.

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 action and then Add Now to add the experiment action. Select the Primary-secondary stream single path interruption 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, and configure Guardrail Policy and 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, and after creating the experiment, 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). Primary-secondary stream single path interruption 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 primary-secondary stream single path interruption:
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 the primary-secondary stream disconnection, enter CSS Console > Stream Management page, click Primary and Secondary Stream, and you can see the Primary and Secondary Stream relationship has changed.
2. In CSS Console > Business Monitoring > Exception Events, click Primary and Secondary Stream Events to view Proactive Switchover abnormal events.
3. Downstream Playback will automatically switch to the replica stream after the primary stream disconnects, 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 > Operation Analysis. For details, see Operation Analysis.



ヘルプとサポート

この記事はお役に立ちましたか?

フィードバック