RANGER-5553: Incorrect Tags count reported in SummaryTOTALTAGS metric from /service/metrics/json API#953
Open
RakeshGuptaDev wants to merge 1 commit into
Open
Conversation
… from /service/metrics/json API
59cc10f to
b7addc8
Compare
This file contains hidden or 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
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.
What changes were proposed in this pull request?
The SummaryTOTALTAGS metric returned by the /service/metrics/json API does not accurately reflect the actual number of Tags present in the system. The value appears to be inconsistent or incorrect when compared against the real tag count.
Steps to Reproduce:
Access the /service/metrics/json API.
Locate the SummaryTOTALTAGS metric in the response.
Compare the reported value with the actual number of Tags in the system.
Expected Result:
SummaryTOTALTAGS should match the actual count of Tags.
Actual Result:
SummaryTOTALTAGS displays an incorrect count.
How was this patch tested?
Verified that the SummaryTOTALTAGS metric in the /service/metrics/json API correctly reflects the actual count of Tags present in the system.