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

manila: resilience against temporarily missing metrics #467

Merged
merged 1 commit into from
May 23, 2024

Conversation

majewsky
Copy link
Contributor

Metrics are sometimes away for a few minutes because of a pod restart or network fluke. We don't want to report 0 usage at this point because that will be stored in the historical_usage timeseries and confuse the quota calculation.

Metrics are sometimes away for a few minutes because of a pod restart or
network fluke. We don't want to report 0 usage at this point because
that will be stored in the historical_usage timeseries and confuse the
quota calculation.
@coveralls
Copy link

Coverage Status

coverage: 79.459%. remained the same
when pulling 66a7771 on ignore-metrics-glitches
into a9da7af on master.

@majewsky majewsky merged commit 00e0d1e into master May 23, 2024
7 checks passed
@majewsky majewsky deleted the ignore-metrics-glitches branch May 23, 2024 11:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants