From ad49d05780cc5994182d87edfc26c937fee80986 Mon Sep 17 00:00:00 2001 From: Amnon Heiman Date: Tue, 17 May 2016 11:29:51 +0300 Subject: [PATCH] ClientRequestMetrics: Using the APITimer The APITimer uses a different endpoint not to break existing API. Signed-off-by: Amnon Heiman --- .../org/apache/cassandra/metrics/ClientRequestMetrics.java | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/main/java/org/apache/cassandra/metrics/ClientRequestMetrics.java b/src/main/java/org/apache/cassandra/metrics/ClientRequestMetrics.java index 8194a53..6fb8718 100644 --- a/src/main/java/org/apache/cassandra/metrics/ClientRequestMetrics.java +++ b/src/main/java/org/apache/cassandra/metrics/ClientRequestMetrics.java @@ -59,12 +59,13 @@ public class ClientRequestMetrics extends LatencyMetrics { public ClientRequestMetrics(String url, String scope) { super(url, "ClientRequest", scope); - timeouts = APIMetrics.newMeter(url + "/timeouts", + timeouts = APIMetrics.newMeter(url + "/timeouts_rates", factory.createMetricName("Timeouts"), "timeouts", TimeUnit.SECONDS); - unavailables = APIMetrics.newMeter(url + "/unavailables", + unavailables = APIMetrics.newMeter(url + "/unavailables_rates", factory.createMetricName("Unavailables"), "unavailables", TimeUnit.SECONDS); + } public void release() {