-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dev, v3.0: add monitoring TiDB in K8s and log collecting #1552
dev, v3.0: add monitoring TiDB in K8s and log collecting #1552
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When your the content in this PR is ready, please also make the same changes to v3.0
.
@@ -0,0 +1,59 @@ | |||
--- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please put this file to /how-to/monitor/tidb-in-kubernetes.md
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should log collecting doc been moved to the same folder as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@AstroProfundis Not necessarily. Please keep it in /how-to/maintain/tidb-in-kubernetes/
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please put this file to /how-to/monitor/tidb-in-kubernetes.md
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Co-Authored-By: Lilian Lee <lilin@pingcap.com>
Important Update: We have added a markdownlint static check in the CI check to improve the quality of our documentation, so your unclosed PR might fail the CI check now. First, you should merge master to your branch, so the upstream changes might resolve the issues found by the CI check. Then, click @AstroProfundis If you have any problem with troubleshooting, please consult @yikeke for help. Thanks for your cooperation~ Ref: #1494 |
@yikeke PTAL |
@@ -0,0 +1,59 @@ | |||
--- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please put this file to /how-to/monitor/tidb-in-kubernetes.md
.
@AstroProfundis Please address the last comment. That file directory and file name are incorrect. Just keep it consistent with that in |
@lilin90 PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I'll add the two new files to |
What is changed, added or deleted?
Checklist
TOC.md
title
in metadataTOC.md