Automated Traffic Rule Inspection with Flow Replay Platform

Background: The production stability was ensured using various methods such as online error log monitoring, data verification, front‑end inspection, traffic replay, and interface automation, but each had high false‑positive rates or limited coverage.

Traffic replay advantage: It can capture traffic from all environments (online, pre‑release, offline), including sub‑calls, parameters and responses. By writing simple business rule checks, the replay traffic can be used to verify logic across the whole environment and intercept anomalies.

Investment & benefits: Configured 51 interface rules in Q3, 30 completed; each rule takes about 5‑10 minutes after familiarizing with the platform.

Discovered issues: Examples include coupon amount zero due to virtual product recommendation, inflation amount after coupon equal to pre‑inflation amount, and 520 coupon failures in detail pages caused by missing checks in the query‑coupon interface.

Practice process: Pre‑work: Enable automatic recording for new applications in the traffic replay platform. Rule configuration: Define conditions and assertions (e.g., jsonPath checks) for each scenario, create rules from sample traffic, add jsonPath, configure conditions, and set assertions (single field, comparison, or script). Exception alert: The platform notifies via robot when traffic violates rules, with filtering by interface or environment.

Summary of advantages: Online inspection: Continuous rule‑driven validation in pre‑release and production reduces false alarms. Developer self‑test: Rules run on all environments, integrating with CI pipelines to ensure 100 % issue resolution before release. Demand shift: Validation rules written offline can be reused online during rollout, lowering manual effort. Release verification: Post‑deployment traffic is validated instantly, shortening regression cycles. Offline interception: Automated traffic generation and rule enforcement lower manual verification cost.

Problem‑focused checklist: Highlighted scenarios such as activity‑related interfaces, mandatory C‑end data, user‑visible changes (e.g., coupon success), and algorithmic paths lacking test environments.