summaryrefslogtreecommitdiffstats
path: root/metrics
diff options
context:
space:
mode:
authorArne Juul <arnej@yahoo-inc.com>2018-10-02 13:50:30 +0000
committerArne Juul <arnej@yahoo-inc.com>2018-10-03 19:47:51 +0000
commit681131071c937129c2cf492098ca47a79c7e6203 (patch)
treee824c826a1d3bad39c157d6ac18a81e1480355fa /metrics
parent7e953a8f8e02a002323c789405d8c05c7e3518ab (diff)
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.
Diffstat (limited to 'metrics')
-rw-r--r--metrics/src/tests/metricmanagertest.cpp2
1 files changed, 1 insertions, 1 deletions
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)