Handle prometheus normalization breaking change #2366
Merged
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
Signed-off-by: Raphael Silva <[email protected]>
bryan-aguilar
approved these changes
Sep 22, 2023
Signed-off-by: Raphael Silva <[email protected]>
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: Handle prometheus normalization breaking change
This PR will give users one more release of time to absorb the changes in the behaviour of the normalization of prometheus exporters, as a result of this change being merged upstream.
Link to tracking Issue: #2367
Testing: I will use the CI to validate this change.
Documentation: In #2367
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.