<fix>[zwatch]: migrate VRouter CPU alarm metric

[ZStack-Robot]

ZSTAC-86505

Root Cause

The one-click VPC router CPU alarm should evaluate against external monitoring data. Existing active alarm templates and alarms still reference VRouterCPUAverageUsedUtilization, so recovery/current values can mismatch the intended trigger metric.

Fix

Add a 5.4.10 schema migration that moves the VPC router CPU active alarm template and existing linked alarms to CPUUsedUtilization.

Upgrade Idempotence

Both UPDATE statements are guarded by the old metric name. After the first run, rows no longer match VRouterCPUAverageUsedUtilization, so re-running the upgrade has no additional effect.

Test

• Conflict was resolved by moving the source V5.5.12 SQL into conf/db/upgrade/V5.4.10__schema.sql.
• git diff --check upstream/5.4.10..HEAD passed.

Related MRs

• premium MR: pending

Related: ZSTAC-86505, ZSTAC-79949

sync from gitlab !10396

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 6 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: a39f3e3f-3ff3-4a87-95aa-3e01fef90bbd

📥 Commits

Reviewing files that changed from the base of the PR and between 08177ca and 33beb74.

📒 Files selected for processing (1)

• conf/db/upgrade/V5.4.10__schema.sql

Warning

.coderabbit.yaml has a parsing error

The CodeRabbit configuration file in this repository has a parsing error and default settings were used instead. Please fix the error(s) in the configuration file. You can initialize chat with CodeRabbit to get help with the configuration file.

💥 Parsing errors (1)

Could not fetch remote config from http://open.zstack.ai:20001/code-reviews/zstack-cloud.yaml: TimeoutError: The operation was aborted due to timeout

⚙️ Configuration instructions

• Please see the configuration documentation for more information.
• You can also validate your configuration using the online YAML validator.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch sync/yaohua.wu/bugfix/ZSTAC-86505@@2

---

_{Comment @coderabbitai help to get the list of available commands.}