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.
This commit is contained in:
Aliaksandr Valialkin 2019-10-31 13:29:14 +02:00
parent e76e21e4c7
commit 86f6be40db

View File

@ -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 * `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. 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 * `vm_rows{type="indexdb"}` - the number of rows in inverted index. High value for this number usually mean high churn rate for time series.
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.
* Sum of `vm_rows{type="storage/big"}` and `vm_rows{type="storage/small"}` - total number of `(timestamp, value)` data points * Sum of `vm_rows{type="storage/big"}` and `vm_rows{type="storage/small"}` - total number of `(timestamp, value)` data points
in the database. in the database.
* Sum of all the `vm_cache_size_bytes` metrics - the total size of all the caches in the database. * Sum of all the `vm_cache_size_bytes` metrics - the total size of all the caches in the database.