summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChris Akritidis <43294513+cakrit@users.noreply.github.com>2023-04-13 08:50:24 -0700
committerGitHub <noreply@github.com>2023-04-13 08:50:24 -0700
commit40f69dc20f7e40b7155d29a3f735ec4af29f4865 (patch)
tree014cb94edbd822ca1c25a57a90704443a1021821
parent238cb29793398cb258efb9a56bf031e9c00a858e (diff)
Update change-metrics-storage.md (#14905)
-rw-r--r--docs/store/change-metrics-storage.md3
1 files changed, 3 insertions, 0 deletions
diff --git a/docs/store/change-metrics-storage.md b/docs/store/change-metrics-storage.md
index 495a1fb61a..a7d7e77456 100644
--- a/docs/store/change-metrics-storage.md
+++ b/docs/store/change-metrics-storage.md
@@ -3,6 +3,8 @@
The Netdata Agent uses a custom made time-series database (TSDB), named the
[`dbengine`](https://github.com/netdata/netdata/blob/master/database/engine/README.md), to store metrics.
+To see the number of metrics stored and the retention in days per tier, use the `/api/v1/dbengine_stats` endpoint.
+
To increase or decrease the metric retention time, you just [configure](#configure-metric-retention)
the number of storage tiers and the space allocated to each one. The effect of these two parameters
on the maximum retention and the memory used by Netdata is described in detail, below.
@@ -73,6 +75,7 @@ usually constant over time (affecting compression efficiency). The number of res
through time (because it has to break pages prematurely, increasing the metadata overhead). But the actual
numbers should not deviate significantly from the above.
+To see the number of metrics stored and the retention in days per tier, use the `/api/v1/dbengine_stats` endpoint.
### Effect of storage tiers and retention on memory usage