-
Notifications
You must be signed in to change notification settings - Fork 682
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
add 3 monitoring documents #2791
add 3 monitoring documents #2791
Conversation
Please help review this PR~ @lilin90 |
tidb-monitoring-api.md
Outdated
|
||
- TiDB API address: `http://${host}:${port}` | ||
- Default port: `10080` | ||
- Details about API names: see [TiDB HTTP API](https://github.com/pingcap/tidb/blob/master/docs/tidb_http_api.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.
Could you provide the source of this line? Because I didn't see it on the Chinese dev
version.
Co-authored-by: Lilian Lee <[email protected]>
@lilin90 All comments are addressed, PTAL again, thanks! |
@TomShawn, please update your pull request. |
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
@TomShawn Please resolve the conflict. |
@TomShawn, please update your pull request. |
…ploy.md-and-tidb-monitoring-api.md
@lilin90 Conflict resolved, PTAL again, thanks! |
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
Signed-off-by: ti-srebot <[email protected]>
cherry pick to release-4.0 in PR #2917 |
Signed-off-by: ti-srebot <[email protected]> Co-authored-by: TomShawn <[email protected]>
What is changed, added or deleted? (Required)
Create monitor-deploy.md and tidb-monitoring-api.md
Which TiDB version(s) do your changes apply to? (Required)
If you select two or more versions from above, to trigger the bot to cherry-pick this PR to your desired release version branch(es), you must add corresponding labels such as needs-cherry-pick-4.0, needs-cherry-pick-3.1, needs-cherry-pick-3.0, and needs-cherry-pick-2.1.
What is the related PR or file link(s)?