Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(azuremonitorreceiver): Azure Monitor receiver should not produce gaps in data points for PT1M time grains #37342

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

an-mmx
Copy link
Contributor

@an-mmx an-mmx commented Jan 20, 2025

Description

The current implementation of tracking for the last metrics fetch is highly sensitive to time, relying on time.Now(). This sensitivity causes the loss of data points due to jitter in 1-minute intervals. I recommend a change request to implement a more robust comparison with the last minute of metrics fetch.

Link to tracking issue

Fixes #37337

Testing

A new coverage introduced in unit test

Documentation

No documentation added

@an-mmx an-mmx requested a review from a team as a code owner January 20, 2025 14:56
@an-mmx an-mmx requested a review from bogdandrutu January 20, 2025 14:56
@github-actions github-actions bot requested a review from nslaughter January 20, 2025 14:56
@an-mmx an-mmx force-pushed the fix/azure-monitor-receiver-time-grain branch 5 times, most recently from f974529 to ee3a095 Compare January 20, 2025 18:10
@an-mmx an-mmx force-pushed the fix/azure-monitor-receiver-time-grain branch from ee3a095 to 9783d0e Compare January 22, 2025 19:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Azure Monitor receiver doesn't honor time grain
2 participants