Cluster configuration - Application Real-Time Monitoring Service

Go to the Cluster Configuration tab

Log on to the ARMS console .
In the left-side navigation pane, click Kubernetes Monitoring.
In the top navigation bar of the MNS console, select the region where your cluster is deployed.
On the Kubernetes Monitoring page, click the name of the Kubernetes cluster that you want to manage.
In the left-side navigation pane, click Cluster management.
On the page that appears, click the Cluster Configuration tab and set the parameters as required. After you set the parameters, click Save.

Global settings

In the Global section, you can change the default ports that are used by Kubernetes Monitoring to collect metrics of the MySQL, Redis, and Kafka protocols.

Notice After the ports are changed, the ARMS agent for Kubernetes Monitoring automatically restarts for the changes to take effect.


Protocol	Default port	Description
MySQL	3306	The port that is used by Kubernetes Monitoring to collect MySQL-related metrics. You can specify multiple ports. Separate multiple ports with commas (,).
Redis	6379	The port that is used by Kubernetes Monitoring to collect Redis-related metrics. You can specify multiple ports. Separate multiple ports with commas (,).
Kafka	9092	The port that is used by Kubernetes Monitoring to collect Kafka-related metrics. You can specify multiple ports. Separate multiple ports with commas (,).

Metric settings

In the Indicators section, you can specify whether to collect the details about metrics and topologies.

Notice The modifications to metric settings immediately take effect without the need to restart the corresponding ARMS agent.


Parameter	Default value	Description
Detailed Metric Data	Enabled	Specifies whether to display the number of requests, response time, number of errors, and number of slow requests for a pod on the details page of the pod.
Detailed Topology Metrics	Disabled	Specifies whether to display the topological details of a pod on the details page of the pod.

Trace-related settings

In the Link section, you can specify the thresholds for slow requests and the sampling rates.

Notice The modifications to trace-related settings immediately take effect without the need to restart the corresponding ARMS agent.


Parameter	Default value	Description
Collect Abnormal Data	Enabled	Specifies whether to display the details of the top API operations that are ranked based on the values of the following protocol-related metrics: the number of requests, response time, number of errors, and number of slow requests.
HTTP Slow Request Threshold	500	The threshold of HTTP slow requests. Unit: milliseconds.
MySQL Slow Request Threshold	500	The threshold for determining a slow MySQL-based request. If the response time to a MySQL-based request exceeds this threshold, the request is considered slow. Unit: milliseconds.
Redis Slow Request Threshold	500	The threshold for determining a slow Redis-based request. If the response time to a Redis-based request exceeds this threshold, the request is considered slow. Unit: milliseconds.
Kafka Slow Request Threshold	500	The threshold for determining a slow Kafka-based request. If the response time to a Kafka-based request exceeds this threshold, the request is considered slow. Unit: milliseconds.
Slow Request Threshold	500	The threshold for determining a slow request based on other protocols. If the response time to a request exceeds this threshold, the request is considered slow. Unit: milliseconds.
Data Sampling Rate on Normal Traces	1	The data sampling rate on a trace in which the response to a business request is normal. Unit: %. Valid values: 0 to 100.
Data Sampling Rate on Slow Traces	100	The data sampling rate on a trace in which the response to a business request is delayed. Unit: %. Valid values: 0 to 100.
Data Sampling Rate on Error Traces	100	The data sampling rate on a trace in which a business request fails to be responded. Unit: %. Valid values: 0 to 100.