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

Inaccurate Reporting of Gauge Metrics in Legacy Metrics Implementation #1379

Closed
VinozzZ opened this issue Oct 10, 2024 · 1 comment
Closed
Labels
status: discussion needed Needs to be discussed with the team type: discussion Requests for comments, discussions about possible enhancements.

Comments

@VinozzZ
Copy link
Contributor

VinozzZ commented Oct 10, 2024

The current implementation of Gauge metrics in the Legacy Metrics system only stores the latest value for each metrics key. As a result, during a metrics reporting interval, only the most recent value is captured and reported.

This behavior can lead to inaccurate metrics under certain conditions:

  • If values are updated frequently, but the reporting interval is set to a longer duration, the final reported value may not accurately reflect the range or variability of the data.
  • The reporting may miss intermediate updates, leading to a skewed representation of the actual metric over time.
@VinozzZ VinozzZ added type: discussion Requests for comments, discussions about possible enhancements. status: discussion needed Needs to be discussed with the team labels Oct 10, 2024
@VinozzZ
Copy link
Contributor Author

VinozzZ commented Oct 17, 2024

This is how Gauge metric work. Closing the issue

@VinozzZ VinozzZ closed this as completed Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: discussion needed Needs to be discussed with the team type: discussion Requests for comments, discussions about possible enhancements.
Projects
None yet
Development

No branches or pull requests

1 participant