[receiver/azuremonitor] Fix metric data loss and incorrect timestamps#49532
Open
vishalmore90 wants to merge 1 commit into
Open
[receiver/azuremonitor] Fix metric data loss and incorrect timestamps#49532vishalmore90 wants to merge 1 commit into
vishalmore90 wants to merge 1 commit into
Conversation
Signed-off-by: vishal <httpsvishal07@gmail.com>
vishalmore90
force-pushed
the
fix-issue-49508
branch
from
d9e5765 to
b8921e8
Compare
vishalmore90
changed the title
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
1 participant
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
Fixes metric data loss and incorrect timestamping in the
azuremonitorreceiver:resourceID + metricName + dimensions) to filter out already-emitted historical data.scraper.go) instead of replacing them withtime.Now().Fixes #49508
Testing
Unit tests updated to verify correct chronological ordering of multiple data points, use of correct Azure timestamps, and no duplicate emissions on subsequent scrapes.