i18n(ja): restore literal English metric names in TiDB Cloud monitoring docs - #23751
Conversation
…ng docs Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Team Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review. 📝 WalkthroughWalkthroughThe monitoring documentation replaces Japanese metric names and labels with English names from the Metrics UI. Japanese metric descriptions remain in the Dedicated, Starter, Essential, and Premium tables. ChangesMonitoring metric documentation
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to Monitoring documentation now matches the English metric and label names shown in the UI while preserving Japanese explanatory text. The documentation-only update is ready to merge. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
[LGTM Timeline notifier]Timeline:
|
What is changed, added or deleted? (Required)
Restores the literal English metric/panel names in TiDB Cloud built-in monitoring docs. The Metric name column in these dashboard tables must contain the literal panel name exactly as shown on the actual TiDB Cloud Metrics page in the product UI (for example, "Database Time by SQL types", "Query Per Second"). The Japanese translation had translated these literal names into Japanese descriptive phrases instead of keeping the literal English UI text. Also restored the accompanying Labels column values where the EN source itself presents them as literal legend/series values (e.g.
{SQL type},hit,miss,All,avg-in-txn) rather than descriptive prose.tidb-cloud/built-in-monitoring.md: 5 tables (Overview, Advanced, Server for Dedicated; Instance Overview, Database Status for Starter/Essential) — 58 Metric-name/Labels cells restored to literal English.tidb-cloud/premium/built-in-monitoring-premium.md: 3 tables (Overview, Database, Advanced) — 24 Metric-name/Labels cells restored to literal English.Description columns (free translated prose) were left unchanged.
Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
AI agent involvement
Do your changes match any of the following descriptions?
Summary by CodeRabbit