[receiver/vcenter] Removes vcenter.cluster.memory.effective Metric
#32806
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
atoulme
approved these changes
May 10, 2024
|
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
|
@StefanKurek, is this PR still relevant? |
@djaglowski nope. I actually took care of this along with other cleanup tasks in a different PR. I'll close this now. |
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.
Description:
This metric was never actually implemented, and removing it completely vs. implementing it makes more sense.
Link to tracking Issue:
#32805
Testing:
Unit/integration tests updated and tested. Local environment tested.
Documentation:
New documentation generated based on the metadata.