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
Our current approach to instrumenting ZIO metrics breaks if their mapping functions are used. A better approach would be to interact directly with ConcurrentMetricRegistry. It does provide two approaches - pull based snapshots and push based listeners. Currently push based 'listeners' have at least one issue with them that makes them non-ideal to use - see zio/zio#7897 (comment). We should implement pull based snapshots approach now, maybe consider implementing push based listeners approach in the future and allow users of the Mesmer to toggle which one they want to use.
Our current approach to instrumenting ZIO metrics breaks if their mapping functions are used. A better approach would be to interact directly with
ConcurrentMetricRegistry
. It does provide two approaches - pull basedsnapshots
and push basedlisteners
. Currently push based 'listeners' have at least one issue with them that makes them non-ideal to use - see zio/zio#7897 (comment). We should implement pull basedsnapshots
approach now, maybe consider implementing push basedlisteners
approach in the future and allow users of the Mesmer to toggle which one they want to use.Should resolve #629 and #423.
The text was updated successfully, but these errors were encountered: