Update monitor-alert-flashduty.md#22385
Update monitor-alert-flashduty.md#22385huoyao1125 wants to merge 17 commits intopingcap:release-8.5from
Conversation
|
Hi @huoyao1125. Thanks for your PR. I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Summary of ChangesHello @huoyao1125, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request updates the documentation for Flashduty alert subscriptions in TiDB Cloud. The primary goal is to inform users that alert notifications are now supported across both Dedicated and Essential cluster tiers, and to provide clear, tier-specific instructions for managing these subscriptions. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request updates the Flashduty alert subscription documentation to include instructions for TiDB Cloud Essential clusters. The changes are well-structured, separating instructions for Dedicated and Essential tiers. My review includes a correction for a broken link and a minor stylistic suggestion to improve conciseness, adhering to the repository's style guide.
|
[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 |
|
/ok-to-test |
|
/retest |
| ### Performance Overview alerts | ||
|
|
||
| | Condition | Recommended Action | | ||
| |:--- |:--- | | ||
| | The Request Unit/s exceeded 80% of Max RCU | Suggested actions: <ol><li>Check your traffic pattern in the RU metrics to determine if it is a gradual increase or a sharp spike.</li><li>If it is a gradual increase, verify if Query Duration has increased. If yes, your current max RCU configuration is likely insufficient.</li><li>Scale up your capacity by manually increasing the max RCU in the TiDB Cloud console to meet demand.</li></ol><br/>If the problem cannot be fixed by your side, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) for further assistance.| | ||
| | QPS suddenly dropped by 80% | Suggested actions:<ol><li>Check if it's caused by increasing query latency.</li><li>Check if your application is healthy. If this drop is intentional, ignore this alert. If this drop is not intentional and you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.</li></ol>| | ||
| | Query P99 latency exceeded 200 ms | Recommended Actions:<ol><li>Investigate Slow Queries: Go to Slow Query page. Filter by the recent time range to find newly appeared or slower-running queries.</li><li>Review Recent Changes: Was there a recent application deployment, schema change, or data import job that could explain the change in traffic pattern?</li></ol><br/>If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.| | ||
| | Query P95 latency exceeded 200 ms | Recommended Actions:<ol><li>Investigate slow queries: go to the Slow Query page and filter by the recent time range to find newly appeared or slower-running queries.</li><li>Review recent changes: was there a recent application deployment, schema change, or data import job that could explain the change in traffic pattern?</li></ol><br/>If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.| | ||
| | Request Error Rate exceeded 10% | Check the recent errors and overall statement execution status for this cluster.| |
There was a problem hiding this comment.
dedicated clusters don't have these three alerts for now

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)?
Do your changes match any of the following descriptions?