From 86f6be40dbe2d39c943f2fec39ccd0d12a19fa21 Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Thu, 31 Oct 2019 13:29:14 +0200 Subject: [PATCH] README.md: update information about `vm_rows{type="indexdb"}` metric The previous information became outdated after v1.28.0, since now each row in the inverted index can refer to multiple time series. --- README.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/README.md b/README.md index b7e8b8c6c..c7a1b4eef 100644 --- a/README.md +++ b/README.md @@ -673,10 +673,7 @@ The most interesting metrics are: * `vm_cache_entries{type="storage/hour_metric_ids"}` - the number of time series with new data points during the last hour aka active time series. -* `vm_rows{type="indexdb"}` - the number of rows in inverted index. Each label in each unique time series adds a single - row into the inverted index. An approximate number of time series in the database may be calculated as - `vm_rows{type="indexdb"} / (avg_labels_per_series + 1)`, where `avg_labels_per_series` is the average number of labels - per each time series. +* `vm_rows{type="indexdb"}` - the number of rows in inverted index. High value for this number usually mean high churn rate for time series. * Sum of `vm_rows{type="storage/big"}` and `vm_rows{type="storage/small"}` - total number of `(timestamp, value)` data points in the database. * Sum of all the `vm_cache_size_bytes` metrics - the total size of all the caches in the database.