cherry-pick: refactor(metrics): remove actor_id label from back-pressure metrics based on metrics level (#18213) #18330
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… based on metrics level (#18213) Signed-off-by: Bugen Zhao <[email protected]>
lmatz
approved these changes
Aug 30, 2024
Graphite Automations"release branch request review" took an action on this PR • (08/30/24)1 reviewer was added to this PR based on xxchan's automation. |
lmatz
approved these changes
Sep 2, 2024
lmatz
approved these changes
Sep 2, 2024
kwannoel
approved these changes
Sep 2, 2024
lmatz
deleted the
bz/remove-actor-label-in-backpressure-metrics-cp-20
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Close #18316.
Checklist
./risedev check(or alias,./risedev c)Documentation
Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.