cloud: add subscribing alert via Lark - #23487
Conversation
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughThis change adds a Lark alert subscription guide, documents Lark support for applicable Connected Care plans, and links the guide from TiDB Cloud table-of-contents pages. ChangesLark Alert Subscription Documentation
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 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 |
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
tidb-cloud/monitor-alert-lark (1)
1-2: 🎯 Functional Correctness | 🟠 Major | 🏗️ Heavy liftAdd the Monitor Alert Lark documentation content before merge.
tidb-cloud/monitor-alert-larkcontains only blank lines. The new documentation page cannot provide Monitor Alert Lark information for the TiDB 8.5 release branch.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 47a63681-67e6-4fc7-9687-1acfe27b3807
📒 Files selected for processing (1)
tidb-cloud/monitor-alert-lark
Adds the Subscribe via Lark alert notification guide, mirroring monitor-alert-webhook.md with Lark-specific configuration, and registers it alongside the other subscription channels in the TOC and Connected Care detail page.
There was a problem hiding this comment.
Actionable comments posted: 2
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 4cd23265-0c04-49ef-94b7-ac9f72e0de16
📒 Files selected for processing (5)
TOC-tidb-cloud-essential.mdTOC-tidb-cloud-premium.mdTOC-tidb-cloud.mdtidb-cloud/connected-care-detail.mdtidb-cloud/monitor-alert-lark.md
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 13ee7a11-bfb5-4fd7-8a3e-7640024ea3b7
📒 Files selected for processing (1)
tidb-cloud/monitor-alert-lark.md
|
[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 |
|
|
||
| <CustomContent plan="essential"> | ||
|
|
||
| - To subscribe to alert notifications of TiDB Cloud, you must have the `Organization Owner` access to your organization or `Project Owner` or `Instance Manager` access to the target instance in TiDB Cloud. |
There was a problem hiding this comment.
In Subscribe via Flashduty | TiDB Docs, the required access is "Organization Owner access to your organization or Project Owner access to the target project". Please double check whether the descriptions should be updated to keep the two consistent.
Co-authored-by: Lilian Lee <lilin@pingcap.com>
First-time contributors' checklist
What is changed, added or deleted? (Required)
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions.
What is the related PR or file link(s)?
AI agent involvement
Do your changes match any of the following descriptions?
Summary by CodeRabbit