Details
-
Task
-
Resolution: Done
-
Major
-
None
-
Cheshire-Cat
-
None
-
1
Description
KV maintains a total of 388 stats.
Some of these stats have high cardinality, such as those that produce histograms.
We want to establish..
- what is the space usage is in terms of MB / hour?
- which stats are responsible the majority of consuming the large space?
- How many high-cardinality stats do we maintain?
- Do we really need 388 stats? Are some redundant / of very limited value?
Approach
- Set-up a single KV node cluster and monitor disk usage over a period of 24 hours
- Repeat with a constant KV low-load
Attachments
Issue Links
- relates to
-
MB-46046 All histogram buckets should be reported in every collection
- Closed
-
MB-47153 Use /_prometheusMetrics*NoTS endpoints for external prometheus use case (for kv only)
- Closed
-
MB-47091 Extend Stats Coverage Period
- Open
-
MB-46422 Remove kv_timings histograms from being stored in Prometheus
- Resolved