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
{{ message }}
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.
I have a simple class that implements the "MetricSet" interface and in the "Map<String, Metric> getMetrics()" method I am getting the HystrixCommandMetrics instances and reporting the current metrics.
I then registered my MetricSet class via the "metrics:register" bean in my Spring configuration. I see the "getMetrics" method called once, but then it is never called again. I am using other MetricsSets, like "com.codahale.metrics.jvm.MemoryUsageGaugeSet" and they work fine. Looking at the code of the other MetricsSet classes I don't see why my class is only called once.
I must be missing something really obvious here.. Any help is appreciated.
public class HystrixCodahaleMetricSet implements MetricSet {
@Override
public Map<String, Metric> getMetrics() {
final Map<String, Metric> gauges = new HashMap<String, Metric>();
// code to add gauges left out for brevity, but is similar to that in the MemoryUsageGaugeSet class
return Collections.unmodifiableMap(gauges);
}
The text was updated successfully, but these errors were encountered:
I have a simple class that implements the "MetricSet" interface and in the "Map<String, Metric> getMetrics()" method I am getting the HystrixCommandMetrics instances and reporting the current metrics.
I then registered my MetricSet class via the "metrics:register" bean in my Spring configuration. I see the "getMetrics" method called once, but then it is never called again. I am using other MetricsSets, like "com.codahale.metrics.jvm.MemoryUsageGaugeSet" and they work fine. Looking at the code of the other MetricsSet classes I don't see why my class is only called once.
I must be missing something really obvious here.. Any help is appreciated.
The text was updated successfully, but these errors were encountered: