From 4a1702dcafec665e2a2efa548505d6d1ed44ea49 Mon Sep 17 00:00:00 2001 From: Benjamin Raskin Date: Thu, 5 Dec 2019 19:25:54 -0500 Subject: [PATCH] [docs] Add docs for num unique time series (#2062) --- docs/faqs/index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/faqs/index.md b/docs/faqs/index.md index 8697e621d8..d617421391 100644 --- a/docs/faqs/index.md +++ b/docs/faqs/index.md @@ -63,9 +63,6 @@ etcdClusters: - **How can I get a heap dump, cpu profile, etc.** See our docs on the [/debug/dump api](../troubleshooting/index.md) -- **How can I see the cardinality of my metrics?** -See the `Ticking` graph on [M3DB dashboard](https://grafana.com/dashboards/8126). - - **How much memory utilization should I run M3DB at?** We recommend not going above 50%. @@ -74,3 +71,6 @@ TBA - **What is the recommended way to create a new namespace?** Refer to the [Namespace configuration guide](../operational_guide/namespace_configuration.md). + +- **How can I see the cardinality of my metrics?** +Currently, the best way is to go to the [M3DB Node Details Dashboard](https://grafana.com/grafana/dashboards/8126) and look at the `Ticking` panel. However, this is not entirely accurate because of the way data is stored in M3DB -- time series are stored inside time-based blocks that you configure. In actuality, the `Ticking` graph shows you how many unique series there are for the most recent block that has persisted. In the future, we plan to introduce easier ways to determine the number of unique time series. \ No newline at end of file