You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both quota gates in monitoringHandler tested config.isQuotaEnabled -- the
function reference rather than a call -- so both were always true and all six
quota metrics were always registered.
Drop the conditionals rather than calling the function. Always registering is
what has actually happened since these checks were written, nothing depends on
the metrics disappearing when quota is off, and gating registration would mean
guarding every metric touch point against a metric that was never created:
crrCacheToProm reached bucketsWithQuota unguarded, and the scuba wrapper
observes its histogram in a finally block, on a path the Veeam capacity route
hits with no quota gating at all.
Behaviour is unchanged -- the six s3_cloudserver_quota_* series are exposed
exactly as before -- so this is a dead code removal.
Issue: CLDSRV-972
0 commit comments