From 681131071c937129c2cf492098ca47a79c7e6203 Mon Sep 17 00:00:00 2001 From: Arne Juul Date: Tue, 2 Oct 2018 13:50:30 +0000 Subject: avoid using old "dimensionkey" concept * adding a "dimensionkey" would add an extra dimension to json reporting, but used the Metric name as the value in that dimension. This means there was no added information at all. Also, the "operationtype" dimension wasn't populated with operation types, even if it looked that way, because it wasn't used directly but was cloned and the actual name would be the loadtype instead, making it very confusing. --- metrics/src/tests/metricmanagertest.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'metrics') diff --git a/metrics/src/tests/metricmanagertest.cpp b/metrics/src/tests/metricmanagertest.cpp index e9934b6dbbb..f5d3a77d671 100644 --- a/metrics/src/tests/metricmanagertest.cpp +++ b/metrics/src/tests/metricmanagertest.cpp @@ -68,7 +68,7 @@ struct SubMetricSet : public MetricSet SubMetricSet::SubMetricSet(const Metric::String & name, MetricSet* owner) - : MetricSet(name, "sub", "sub desc", owner, "sub"), + : MetricSet(name, "sub", "sub desc", owner), val1("val1", "tag4 snaptest", "val1 desc", this), val2("val2", "tag5", "val2 desc", this), valsum("valsum", "tag4 snaptest", "valsum desc", this) -- cgit v1.2.3