Repository navigation
tidb-cloud: add New Relic dashboards for Premium and Essential - #24447
Conversation
|
Hi @Yujie-Xie. 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 Tip We noticed you've done this a few times! Consider joining the org to skip this step and gain 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. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
7a4dddd to
a7c8b5e
Compare
[LGTM Timeline notifier]Timeline:
|
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: qiancai The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/ok-to-test |
What is changed, added or deleted? (Required)
Add New Relic dashboard JSON templates under
tidb-cloud/for TiDB Cloud Premium, Essential, and Essential v2 (instances created on or after July 1, 2026). Follow the dashboard asset naming and placement used in #22662.The three templates are copied byte-for-byte from
artifacts/dashboard/newrelic/intidbcloud/metrics-integrationat commit7ccec7a2731a5709d3d1802ee26a2a4957065a4b. New Relic account IDs remain empty for users to configure during import.Validation: parsed all three files with Python's JSON parser, verified SHA-256 equality with the source files, confirmed all
accountIdsfields are empty, and rangit diff --cached --check. This is an asset-only change; no application code or documentation prose changes.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