Skip to content
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

metrics: add metrics for table memory consumption (#1846) #1885

Merged

Conversation

ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #1846

What problem does this PR solve?

  • Lack of observability of processor's table memory consumption (down from the sorter)

What is changed and how it works?

  • Added two Grafana panels for metrics added for flow control.

Check List

Tests

  • Manual test

Related changes

  • Need to cherry-pick to the release branch
  • Need to update key monitor metrics in both TiCDC document and official document

Release note

  • Add metrics for table memory consumption

@ti-chi-bot ti-chi-bot added do-not-merge/cherry-pick-not-approved component/metrics-logging Metrics and logging component. status/ptal Could you please take a look? size/L Denotes a PR that changes 100-499 lines, ignoring generated files. type/cherry-pick-for-release-5.0 This PR is cherry-picked to release-5.0 from a source PR. labels May 31, 2021
@ti-chi-bot ti-chi-bot requested a review from overvenus May 31, 2021 02:10
@ti-chi-bot ti-chi-bot requested a review from amyangfei May 31, 2021 02:10
@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label May 31, 2021
@lonng lonng added cherry-pick-approved Cherry pick PR approved by release team. and removed do-not-merge/cherry-pick-not-approved labels May 31, 2021
@lonng lonng added this to the v5.0.2 milestone May 31, 2021
@zier-one
Copy link
Contributor

/lgtm

@ti-chi-bot
Copy link
Member Author

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • amyangfei
  • leoppro

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by writing /lgtm in a comment.
Reviewer can cancel approval by writing /lgtm cancel in a comment.

@ti-chi-bot ti-chi-bot added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels May 31, 2021
@amyangfei
Copy link
Contributor

/merge

@ti-chi-bot
Copy link
Member Author

This pull request has been accepted and is ready to merge.

Commit hash: aa94519

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label May 31, 2021
@liuzix
Copy link
Contributor

liuzix commented May 31, 2021

/run-integration-test

@liuzix
Copy link
Contributor

liuzix commented May 31, 2021

/run-kafka-integration-test

@liuzix
Copy link
Contributor

liuzix commented May 31, 2021

/run-all-tests

@ti-chi-bot ti-chi-bot merged commit 75fb304 into pingcap:release-5.0 May 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherry-pick-approved Cherry pick PR approved by release team. component/metrics-logging Metrics and logging component. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. status/ptal Could you please take a look? type/cherry-pick-for-release-5.0 This PR is cherry-picked to release-5.0 from a source PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants