[DOC-779] Added metrics collection level (#28677)

* added metrics collection level

* typo fix

* changes from review

* updtaed table

* minor edits from review

Author: aishwarya24

docs/content/preview/yugabyte-platform/administer-yugabyte-platform/manage-runtime-config.md

@@ -22,12 +22,12 @@ YugabyteDB Anywhere has a runtime configuration mechanism that is fully compatib
 
 Currently, the scopes can be categorized as follows:
 
-| Scope | Description | User Access |
+| Scope | Description |
 |:--- |:--- | :--- |
-| Global | Applies to the entire platform, persists across installs and any value defined in this scope overrides the defaults. | Super Admin |
-| Customer | Applies to a specific customer, persists across installs and any value defined in this scope overrides defaults in Global scope.| Super&nbsp;Admin,<br>Admin |
-| Provider | Applies to a specific provider, persists across installs and any value defined in this scope overrides defaults in Customer scope. | Super Admin,<br>Admin |
-| Universe | Applies to a specific universe, persists across installs and any value defined in this scope overrides defaults in Customer scope. | Super Admin,<br>Admin |
+| Global | Applies to the entire platform, persists across installs and any value defined in this scope overrides the defaults. Only the Super Admin can set global runtime configuration settings. |
+| Customer | Applies to a specific customer, persists across installs and any value defined in this scope overrides defaults in Global scope. |
+| Provider | Applies to a specific provider, persists across installs and any value defined in this scope overrides defaults in Customer scope. |
+| Universe | Applies to a specific universe, persists across installs and any value defined in this scope overrides defaults in Customer scope. |
 
 For more details about the flags and their scopes, refer to the [list of supported runtime configuration flags](https://github.com/yugabyte/yugabyte-db/blob/master/managed/RUNTIME-FLAGS.md)
 

docs/content/preview/yugabyte-platform/alerts-monitoring/anywhere-metrics.md

@@ -45,6 +45,23 @@ label_replace(
 
 For more information, refer to [Querying Prometheus](https://prometheus.io/docs/prometheus/latest/querying/basics/) in the Prometheus documentation.
 
+## Metrics collection level
+
+The metrics collection level setting controls how many database metrics are collected and stored. It helps balance system performance with monitoring needs, so that you can optimize resource usage based on your specific observability requirements.
+
+Set the metrics collection level by using the **Metrics Collection Level** Universe Runtime Configuration option (config key `yb.metrics.collection_level`). Refer to [Manage runtime configuration settings](../../../yugabyte-platform/administer-yugabyte-platform/manage-runtime-config/).
+
+You can set the collection level to the following:
+
+| Level | Description |
+|:-------|:---------|
+| ALL | Collects all metrics from the database. Not recommended for large databases with a lot of tables, as it can overload the YugabyteDB Anywhere Prometheus instance and cause Out of Memory (OOM) errors on the node where YugabyteDB Anywhere is installed. |
+| NORMAL (default) | Collects all server-level metrics, and essential table-level metrics (required for YugabyteDB Anywhere UI and alerts). |
+| MINIMAL | Collects limited list of server-level metrics (required for YugabyteDB Anywhere UI and alerts), and very limited table-level metrics (required for alerts and table size display). |
+| OFF | Disables metric collection. |
+
+The collection level directly affects what data appears in monitoring interfaces. With NORMAL level, all UI components display full metrics. However, when MINIMAL is configured, most per-table monitoring screens display "No Data" messages, though table size information and essential alerts continue functioning. This provides a way to reduce monitoring overhead while maintaining core operational visibility.
+
 ## Filter metrics
 
 You can display metrics based on different criteria:
@@ -135,7 +152,7 @@ Resource metrics should be considered on a per-node basis.
 | --------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ | --------------------------------- |
 | Total YSQL Ops / sec  | The number of various transaction control operations, such as BEGIN, COMMIT, ROLLBACK, as well as other operations through the YSQL API. | This metric is informational and should not be subject to alerting. You may consider this information while examining alerts on other metrics. | ![Total YSQL Ops / sec](/images/yp/metrics101.png) |
 | YSQL Op Latency (Avg) | The average time taken by various transaction control operations, such as BEGIN, COMMIT, ROLLBACK, as well as other operations through the YSQL API. | This metric is informational and should not be subject to alerting. You may consider this information while examining alerts on other metrics. | ![YSQL Op Latency (Avg)](/images/yp/metrics102.png) |
-| Catalog Cache Misses | During YSQL query processing, system catalog (pg_catalog) tables that live on the YB-Master are cached on the local YSQL backend. This metric counts the number of YSQL catalog cache misses, where the data had to be fetched from the YB-Master. Also broken down by pg_catalog table that triggered the misses. | This metric is informational and should not be subject to alerting. You may consider this information while examining alerts on other metrics. | ![Catalog Cache Misses](/images/yp/metrics114.png) 
+| Catalog Cache Misses | During YSQL query processing, system catalog (pg_catalog) tables that live on the YB-Master are cached on the local YSQL backend. This metric counts the number of YSQL catalog cache misses, where the data had to be fetched from the YB-Master. Also broken down by pg_catalog table that triggered the misses. | This metric is informational and should not be subject to alerting. You may consider this information while examining alerts on other metrics. | ![Catalog Cache Misses](/images/yp/metrics114.png)
 
 ### YCQL advanced
 

docs/content/stable/yugabyte-platform/administer-yugabyte-platform/manage-runtime-config.md

@@ -22,12 +22,12 @@ YugabyteDB Anywhere has a runtime configuration mechanism that is fully compatib
 
 Currently, the scopes can be categorized as follows:
 
-| Scope | Description | User Access |
+| Scope | Description |
 |:--- |:--- | :--- |
-| Global | Applies to the entire platform, persists across installs and any value defined in this scope overrides the defaults. | Super Admin |
-| Customer | Applies to a specific customer, persists across installs and any value defined in this scope overrides defaults in Global scope.| Super&nbsp;Admin,<br>Admin |
-| Provider | Applies to a specific provider, persists across installs and any value defined in this scope overrides defaults in Customer scope. | Super Admin,<br>Admin |
-| Universe | Applies to a specific universe, persists across installs and any value defined in this scope overrides defaults in Customer scope. | Super Admin,<br>Admin |
+| Global | Applies to the entire platform, persists across installs and any value defined in this scope overrides the defaults. Only the Super Admin can set global runtime configuration settings. |
+| Customer | Applies to a specific customer, persists across installs and any value defined in this scope overrides defaults in Global scope. |
+| Provider | Applies to a specific provider, persists across installs and any value defined in this scope overrides defaults in Customer scope. |
+| Universe | Applies to a specific universe, persists across installs and any value defined in this scope overrides defaults in Customer scope. |
 
 For more details about the flags and their scopes, refer to the [list of supported runtime configuration flags](https://github.com/yugabyte/yugabyte-db/blob/master/managed/RUNTIME-FLAGS.md)
 

docs/content/stable/yugabyte-platform/alerts-monitoring/anywhere-metrics.md

@@ -45,6 +45,24 @@ label_replace(
 
 For more information, refer to [Querying Prometheus](https://prometheus.io/docs/prometheus/latest/querying/basics/) in the Prometheus documentation.
 
+## Metrics collection level
+
+The metrics collection level setting controls how many database metrics are collected and stored. It helps balance system performance with monitoring needs, so that you can optimize resource usage based on your specific observability requirements.
+
+Set the metrics collection level by using the **Metrics Collection Level** Universe Runtime Configuration option (config key `yb.metrics.collection_level`). Refer to [Manage runtime configuration settings](../../../yugabyte-platform/administer-yugabyte-platform/manage-runtime-config/).
+
+You can set the collection level to the following:
+
+| Level | Description |
+|:-------|:---------|
+| ALL | Collects all metrics from the database. Not recommended for large databases with a lot of tables, as it can overload the YugabyteDB Anywhere Prometheus instance and cause Out of Memory (OOM) errors on the node where YugabyteDB Anywhere is installed. |
+| NORMAL (default) | Collects all server-level metrics, and essential table-level metrics (required for YugabyteDB Anywhere UI and alerts). |
+| MINIMAL | Collects limited list of server-level metrics (required for YugabyteDB Anywhere UI and alerts), and very limited table-level metrics (required for alerts and table size display). |
+| OFF | Disables metric collection. |
+| TABLE_OFF | Collects only server-level metrics. |
+
+The collection level directly affects what data appears in monitoring interfaces. With NORMAL level, all UI components display full metrics. However, when MINIMAL is configured, most per-table monitoring screens display "No Data" messages, though table size information and essential alerts continue functioning. This provides a way to reduce monitoring overhead while maintaining core operational visibility.
+
 ## Filter metrics
 
 You can display metrics based on different criteria:

docs/content/v2.20/yugabyte-platform/administer-yugabyte-platform/manage-runtime-config.md

@@ -22,12 +22,12 @@ YugabyteDB Anywhere has a runtime configuration mechanism that is fully compatib
 
 Currently, the scopes can be categorized as follows:
 
-| Scope | Description | User Access |
+| Scope | Description |
 |:--- |:--- | :--- |
-| Global | Applies to the entire platform, persists across installs and any value defined in this scope overrides the defaults. | Super Admin |
-| Customer | Applies to a specific customer, persists across installs and any value defined in this scope overrides defaults in Global scope.| Super&nbsp;Admin,<br>Admin |
-| Provider | Applies to a specific provider, persists across installs and any value defined in this scope overrides defaults in Customer scope. | Super Admin,<br>Admin |
-| Universe | Applies to a specific universe, persists across installs and any value defined in this scope overrides defaults in Customer scope. | Super Admin,<br>Admin |
+| Global | Applies to the entire platform, persists across installs and any value defined in this scope overrides the defaults. Only the Super Admin can set global runtime configuration settings. |
+| Customer | Applies to a specific customer, persists across installs and any value defined in this scope overrides defaults in Global scope. |
+| Provider | Applies to a specific provider, persists across installs and any value defined in this scope overrides defaults in Customer scope. |
+| Universe | Applies to a specific universe, persists across installs and any value defined in this scope overrides defaults in Customer scope. |
 
 For more details about the flags and their scopes, refer to the [list of supported runtime configuration flags](https://github.com/yugabyte/yugabyte-db/blob/master/managed/RUNTIME-FLAGS.md)
 

docs/content/v2.20/yugabyte-platform/alerts-monitoring/anywhere-metrics.md

@@ -43,6 +43,23 @@ label_replace(
 
 For more information, refer to [Querying Prometheus](https://prometheus.io/docs/prometheus/latest/querying/basics/) in the Prometheus documentation.
 
+## Metrics collection level
+
+The metrics collection level setting controls how many database metrics are collected and stored. It helps balance system performance with monitoring needs, so that you can optimize resource usage based on your specific observability requirements.
+
+Set the metrics collection level by using the **Metrics Collection Level** Universe Runtime Configuration option (config key `yb.metrics.collection_level`). Refer to [Manage runtime configuration settings](../../../yugabyte-platform/administer-yugabyte-platform/manage-runtime-config/).
+
+You can set the collection level to the following:
+
+| Level | Description |
+|:-------|:---------|
+| ALL | Collects all metrics from the database. Not recommended for large databases with a lot of tables, as it can overload the YugabyteDB Anywhere Prometheus instance and cause Out of Memory (OOM) errors on the node where YugabyteDB Anywhere is installed. |
+| NORMAL (default) | Collects all server-level metrics, and essential table-level metrics (required for YugabyteDB Anywhere UI and alerts). |
+| MINIMAL | Collects limited list of server-level metrics (required for YugabyteDB Anywhere UI and alerts), and very limited table-level metrics (required for alerts and table size display). |
+| OFF | Disables metric collection. |
+
+The collection level directly affects what data appears in monitoring interfaces. With NORMAL level, all UI components display full metrics. However, when MINIMAL is configured, most per-table monitoring screens display "No Data" messages, though table size information and essential alerts continue functioning. This provides a way to reduce monitoring overhead while maintaining core operational visibility.
+
 ## Filter metrics
 
 You can display metrics based on different criteria:

docs/content/v2024.1/yugabyte-platform/administer-yugabyte-platform/manage-runtime-config.md

@@ -22,12 +22,12 @@ YugabyteDB Anywhere has a runtime configuration mechanism that is fully compatib
 
 Currently, the scopes can be categorized as follows:
 
-| Scope | Description | User Access |
+| Scope | Description |
 |:--- |:--- | :--- |
-| Global | Applies to the entire platform, persists across installs and any value defined in this scope overrides the defaults. | Super Admin |
-| Customer | Applies to a specific customer, persists across installs and any value defined in this scope overrides defaults in Global scope.| Super&nbsp;Admin,<br>Admin |
-| Provider | Applies to a specific provider, persists across installs and any value defined in this scope overrides defaults in Customer scope. | Super Admin,<br>Admin |
-| Universe | Applies to a specific universe, persists across installs and any value defined in this scope overrides defaults in Customer scope. | Super Admin,<br>Admin |
+| Global | Applies to the entire platform, persists across installs and any value defined in this scope overrides the defaults. Only the Super Admin can set global runtime configuration settings. |
+| Customer | Applies to a specific customer, persists across installs and any value defined in this scope overrides defaults in Global scope. |
+| Provider | Applies to a specific provider, persists across installs and any value defined in this scope overrides defaults in Customer scope. |
+| Universe | Applies to a specific universe, persists across installs and any value defined in this scope overrides defaults in Customer scope. |
 
 For more details about the flags and their scopes, refer to the [list of supported runtime configuration flags](https://github.com/yugabyte/yugabyte-db/blob/master/managed/RUNTIME-FLAGS.md)
 

docs/content/v2024.1/yugabyte-platform/alerts-monitoring/anywhere-metrics.md

@@ -43,6 +43,24 @@ label_replace(
 
 For more information, refer to [Querying Prometheus](https://prometheus.io/docs/prometheus/latest/querying/basics/) in the Prometheus documentation.
 
+## Metrics collection level
+
+The metrics collection level setting controls how many database metrics are collected and stored. It helps balance system performance with monitoring needs, so that you can optimize resource usage based on your specific observability requirements.
+
+Set the metrics collection level by using the **Metrics Collection Level** Universe Runtime Configuration option (config key `yb.metrics.collection_level`). Refer to [Manage runtime configuration settings](../../../yugabyte-platform/administer-yugabyte-platform/manage-runtime-config/).
+
+You can set the collection level to the following:
+
+| Level | Description |
+|:-------|:---------|
+| ALL | Collects all metrics from the database. Not recommended for large databases with a lot of tables, as it can overload the YugabyteDB Anywhere Prometheus instance and cause Out of Memory (OOM) errors on the node where YugabyteDB Anywhere is installed. |
+| NORMAL (default) | Collects all server-level metrics, and essential table-level metrics (required for YugabyteDB Anywhere UI and alerts). |
+| MINIMAL | Collects limited list of server-level metrics (required for YugabyteDB Anywhere UI and alerts), and very limited table-level metrics (required for alerts and table size display). |
+| OFF | Disables metric collection. |
+| TABLE_OFF | Collects only server-level metrics. |
+
+The collection level directly affects what data appears in monitoring interfaces. With NORMAL level, all UI components display full metrics. However, when MINIMAL is configured, most per-table monitoring screens display "No Data" messages, though table size information and essential alerts continue functioning. This provides a way to reduce monitoring overhead while maintaining core operational visibility.
+
 ## Filter metrics
 
 You can display metrics based on different criteria:

docs/content/v2024.2/yugabyte-platform/administer-yugabyte-platform/manage-runtime-config.md

@@ -22,12 +22,12 @@ YugabyteDB Anywhere has a runtime configuration mechanism that is fully compatib
 
 Currently, the scopes can be categorized as follows:
 
-| Scope | Description | User Access |
+| Scope | Description |
 |:--- |:--- | :--- |
-| Global | Applies to the entire platform, persists across installs and any value defined in this scope overrides the defaults. | Super Admin |
-| Customer | Applies to a specific customer, persists across installs and any value defined in this scope overrides defaults in Global scope.| Super&nbsp;Admin,<br>Admin |
-| Provider | Applies to a specific provider, persists across installs and any value defined in this scope overrides defaults in Customer scope. | Super Admin,<br>Admin |
-| Universe | Applies to a specific universe, persists across installs and any value defined in this scope overrides defaults in Customer scope. | Super Admin,<br>Admin |
+| Global | Applies to the entire platform, persists across installs and any value defined in this scope overrides the defaults. Only the Super Admin can set global runtime configuration settings. |
+| Customer | Applies to a specific customer, persists across installs and any value defined in this scope overrides defaults in Global scope. |
+| Provider | Applies to a specific provider, persists across installs and any value defined in this scope overrides defaults in Customer scope. |
+| Universe | Applies to a specific universe, persists across installs and any value defined in this scope overrides defaults in Customer scope. |
 
 For more details about the flags and their scopes, refer to the [list of supported runtime configuration flags](https://github.com/yugabyte/yugabyte-db/blob/master/managed/RUNTIME-FLAGS.md)