Skip to content

Commit

Permalink
[docs] Add docs for num unique time series (#2062)
Browse files Browse the repository at this point in the history
  • Loading branch information
benraskin92 authored and robskillington committed Dec 6, 2019
1 parent 54cdb87 commit 4a1702d
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions docs/faqs/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -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%.

Expand All @@ -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.

0 comments on commit 4a1702d

Please sign in to comment.