Db audit log beta dedicated - #22889
Conversation
|
Hi @ginkgoch. 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. |
There was a problem hiding this comment.
Code Review
This pull request updates the TiDB Cloud Dedicated Database Audit Logging documentation to reflect its Public Preview status, introduces a legacy guide, and details new configuration steps for log rotation and redaction. Reviewer feedback focuses on correcting grammatical errors, ensuring terminology consistency for Azure storage, and aligning list formatting and capitalization with the style guide.
|
@jusong: adding LGTM is restricted to approvers and reviewers in OWNERS files. DetailsIn response to this: Instructions 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. |
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
|
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:
📝 WalkthroughWalkthroughTiDB Cloud audit logging documentation now covers Public Preview eligibility, updated cloud-storage workflows, settings, limitations, and schemas. A separate legacy reference page was added, and the table of contents now links to both documentation versions. ChangesAudit Logging Documentation
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested labels: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 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.
Actionable comments posted: 3
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 2e4c69ef-264f-4f2d-a81b-b9912681f063
📒 Files selected for processing (3)
TOC-tidb-cloud.mdtidb-cloud/tidb-cloud-auditing-legacy.mdtidb-cloud/tidb-cloud-auditing.md
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
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/tidb-cloud-auditing.md (1)
112-112: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winFix the bucket-region wording.
“Where the bucket locates” is ungrammatical. Replace it with “where the bucket is located.”
Suggested replacement
-2. In the **Bucket Region** drop-down list, select the AWS region where the bucket locates. +2. In the **Bucket Region** drop-down list, select the AWS region where the bucket is located.Source: Path instructions
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 21a4092c-e56f-4943-8465-f1f32f294245
📒 Files selected for processing (2)
tidb-cloud/tidb-cloud-auditing-legacy.mdtidb-cloud/tidb-cloud-auditing.md
| | `TABLES` | The accessed tables related to this audit record. | | ||
| | `STATUS_CODE` | The status code of the audit record. `1` means success, and `0` means failure. | | ||
| | `KEYSPACE_NAME` | The keyspace name of the audit record. | | ||
| | `SERVERLESS_TENANT_ID` | The ID of the serverless tenant that the {{{ .essential }}} instance belongs to. | |
There was a problem hiding this comment.
This is the Dedicated audit logging page and the prerequisites already direct Essential users to a separate document.
| | `SERVERLESS_TENANT_ID` | The ID of the serverless tenant that the {{{ .essential }}} instance belongs to. | |
| | `STATUS_CODE` | The status code of the audit record. `1` means success, and `0` means failure. | | ||
| | `KEYSPACE_NAME` | The keyspace name of the audit record. | | ||
| | `SERVERLESS_TENANT_ID` | The ID of the serverless tenant that the {{{ .essential }}} instance belongs to. | | ||
| | `SERVERLESS_PROJECT_ID` | The ID of the serverless project that the {{{ .essential }}} instance belongs to. | |
There was a problem hiding this comment.
Same issue as above: this serverless-only field belongs in the Essential audit logging doc, not the Dedicated doc.
| | `SERVERLESS_PROJECT_ID` | The ID of the serverless project that the {{{ .essential }}} instance belongs to. | |
| | `KEYSPACE_NAME` | The keyspace name of the audit record. | | ||
| | `SERVERLESS_TENANT_ID` | The ID of the serverless tenant that the {{{ .essential }}} instance belongs to. | | ||
| | `SERVERLESS_PROJECT_ID` | The ID of the serverless project that the {{{ .essential }}} instance belongs to. | | ||
| | `SERVERLESS_CLUSTER_ID` | The ID of the serverless {{{ .essential }}} instance that the audit record belongs to. | |
There was a problem hiding this comment.
Same issue as above: this serverless-only field belongs in the Essential audit logging doc, not the Dedicated doc.
| | `SERVERLESS_CLUSTER_ID` | The ID of the serverless {{{ .essential }}} instance that the audit record belongs to. | |
|
[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 |
First-time contributors' checklist
What is changed, added or deleted? (Required)
We are going to public preview audit log v2, so documents are update accordingly. V1 document is still keep for existing user for reference.
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?
Summary by CodeRabbit
New Documentation
Documentation