Update change-metrics-storage.md (#14641)
Chris Akritidis committed
Mar 1, 2023 at 06:55 UTC
02fa760a4403e857ae3b6b7019c991b676df0f71
1 file changed
+4
-3
docs/store/change-metrics-storage.md
+4
-3
@@ -48,10 +48,11 @@ on the maximum retention and the memory used by Netdata is described in detail,
48
The default "update every iterations" of 60 means that if a metric is collected per second in Tier 0, then
49
we will have a data point every minute in tier 1 and every minute in tier 2.
50
51
-You may add, or remove tiers and/or modify these multipliers, as long as the product of all the "update every" does not exceed 65535.
51
+Up to 5 tiers are supported. You may add, or remove tiers and/or modify these multipliers, as long as the
52
+product of all the "update every iterations" does not exceed 65535 (number of points for each tier0 point).
53
53
-e.g. If you simply add a fourth tier by setting `storage tiers` to 4 and defining the disk space for it,
54
-the product of the update every will be 60 * 60 * 60 = 216,000, which is > 65535. So you'd need to reduce
54
+e.g. If you simply add a fourth tier by setting `storage tiers = 4` and defining the disk space for the new tier,
55
+the product of the "update every iterations" will be 60 * 60 * 60 = 216,000, which is > 65535. So you'd need to reduce
56
the `update every iterations` of the tiers, to stay under the limit.
57
58
The exact retention that can be achieved by each tier depends on the number of metrics collected. The more