I'm trying to capture Cassandra client-side query latency metrics using Micrometer. Cassandra Java driver exposes some metrics through Dropwizard, but there's no way to bridge Dropwizard -> Micrometer for general meters like timers and histograms; Dropwizard MetricRegistryListener methods are invoked after a meter has been added to the registry, thus eliminating any chance of interception.
If the methods in a MetricRegistryListener are invoked before a meter has been added to the registry, clients may choose to proxy/wrap desired meters, thus making it possible to easily collect metrics using the library of their choice.
asarkar
commented
5 years ago
I'm trying to capture Cassandra client-side query latency metrics using Micrometer. Cassandra Java driver exposes some metrics through Dropwizard, but there's no way to bridge Dropwizard -> Micrometer for general meters like timers and histograms; Dropwizard
MetricRegistryListenermethods are invoked after a meter has been added to the registry, thus eliminating any chance of interception.If the methods in a
MetricRegistryListenerare invoked before a meter has been added to the registry, clients may choose to proxy/wrap desired meters, thus making it possible to easily collect metrics using the library of their choice.