OBSDOCS-1938: Show how to increase metrics-server verbosity

Author: eromanova97

modules/monitoring-setting-log-levels-for-monitoring-components.adoc

@@ -37,6 +37,13 @@ The following log levels can be applied to the relevant component in the `{confi
 
 The default log level is `info`.
 
+// tag::CPM[]
+[NOTE]
+====
+The Metrics Server component uses a different logging configuration method. For more information, see "Setting log verbosity for Metrics Server".
+====
+// end::CPM[]
+
 .Prerequisites
 
 // tag::CPM[]

modules/monitoring-setting-log-verbosity-for-metrics-server.adoc

@@ -0,0 +1,62 @@
+// Module included in the following assemblies:
+//
+// * observability/monitoring/configuring-core-platform-monitoring/storing-and-recording-data.adoc
+
+:_mod-docs-content-type: PROCEDURE
+[id="setting-log-verbosity-for-metrics-server_{context}"]
+= Setting log verbosity for Metrics Server
+
+You can configure the log verbosity for the Metrics Server component to control the level of detail in the log output. You can use this setting for troubleshooting and better insight into how the Metrics Server is functioning.
+
+[NOTE]
+====
+Setting a higher verbosity level can help diagnose issues, but it might increase log volume significantly.
+====
+
+.Prerequisites
+
+* You have access to the cluster as a user with the `cluster-admin` cluster role.
+* You have created the `cluster-monitoring-config` `ConfigMap` object.
+* You have installed the OpenShift CLI (`oc`).
+
+.Procedure
+
+. Edit the `cluster-monitoring-config` config map in the `openshift-monitoring` project:
++
+[source,terminal]
+----
+$ oc -n openshift-monitoring edit configmap cluster-monitoring-config
+----
+
+. Add the `verbosity` parameter under `data/config.yaml/metricsServer`:
++
+.Example verbosity setting for Metrics Server
+[source,yaml]
+----
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: cluster-monitoring-config
+  namespace: openshift-monitoring
+data:
+  config.yaml: |
+    metricsServer:
+      verbosity: 3 # <1>
+    # ...
+----
+<1> Valid values are positive integers. Increasing the value increases the number of logged events, values over `10` are usually unnecessary. The default value is `0`.
+
+. Save the file to apply the changes. The pods affected by the new configuration are automatically redeployed.
+
+. Verify that the log verbosity is applied by running the following command:
++
+[source,terminal]
+----
+$ oc -n openshift-monitoring get pod <metrics_server_pod_name> -o yaml | grep -- --v=
+----
++
+.Example output
+[source,terminal]
+----
+    - --v=3
+----

observability/monitoring/configuring-core-platform-monitoring/storing-and-recording-data.adoc

@@ -44,6 +44,9 @@ include::modules/monitoring-modifying-retention-time-and-size-for-prometheus-met
 // Configuring audit logs for Metrics Server
 include::modules/monitoring-configuring-audit-logs-for-metrics-server.adoc[leveloffset=+1]
 
+// Setting log verbosity for Metrics Server
+include::modules/monitoring-setting-log-verbosity-for-metrics-server.adoc[leveloffset=+1]
+
 // Setting log levels for monitoring components
 include::modules/monitoring-setting-log-levels-for-monitoring-components.adoc[leveloffset=+1,tags=**;CPM;!UWM]