Metrics implementation has never been finished. As such, it is an abstraction which provides very little utility to its users.
It seems to be an idea of combining Dropwizard and Prometheus, yet those serve different purposes and scopes. At the end of the day, Prometheus client and Metrics Core provide the same instrumentation entrypoints.
Instead of providing a framework to hide these, we should let applications choose what to do. One example would be to standardize on Dropwizard (as The Java Thing(tm)) and bridging it to Prometheus (as The Containers Thing(tm)) via a bridge .
As the user seems to be serviceutils, rehost the component there. It new identity will reflect its placement.
Metrics implementation has never been finished. As such, it is an abstraction which provides very little utility to its users.
It seems to be an idea of combining Dropwizard and Prometheus, yet those serve different purposes and scopes. At the end of the day, Prometheus client and Metrics Core provide the same instrumentation entrypoints.
Instead of providing a framework to hide these, we should let applications choose what to do. One example would be to standardize on Dropwizard (as The Java Thing(tm)) and bridging it to Prometheus (as The Containers Thing(tm)) via a bridge .
As the user seems to be serviceutils, rehost the component there. It new identity will reflect its placement.