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
Components that update metrics receive metrics instance via configuration.
First we may refactor components to make metrics configurable and fallback to metrics.Default for backwards compatibility.
Then deprecate and later remove metrics.Default completely.
Would you like to work on it?
Yes
The text was updated successfully, but these errors were encountered:
Use configed metrics and fallback to global for backwards compatibility.
Updates #3026
Signed-off-by: Alexander Yastrebov <alexander.yastrebov@zalando.de>
Use configed metrics and fallback to global for backwards compatibility.
Updates #3026
Signed-off-by: Alexander Yastrebov <alexander.yastrebov@zalando.de>
Is your feature request related to a problem? Please describe.
There are quite a few places that rely on global metrics.Default variable
skipper/metrics/metrics.go
Lines 199 to 202 in 0ce11b9
This is a bad design which is not thread-safe and complicates tests, e.g.:
skipper/proxy/metrics_test.go
Lines 19 to 24 in 0ce11b9
Describe the solution you would like
Components that update metrics receive metrics instance via configuration.
First we may refactor components to make metrics configurable and fallback to metrics.Default for backwards compatibility.
Then deprecate and later remove
metrics.Default
completely.Would you like to work on it?
Yes
The text was updated successfully, but these errors were encountered: