Monitoring reveals that the ng-monitoring-server process suddenly consumes a large amount of memory

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 监控发现ng-monitoring-server进程突然占用大量内存

| username: TiDBer_vZIeuSNY

[TiDB Usage Environment] Production Environment
[TiDB Version] v6.5.1
[Reproduction Path]
[Encountered Problem: Problem Phenomenon and Impact]
[Resource Configuration] Enter TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachments: Screenshots/Logs/Monitoring]
Monitoring found that the ng-monitoring-server process suddenly occupied a large amount of memory. The logs do not show why. Under what circumstances would the ng-monitoring-server process occupy a large amount of memory?

image
image906×273 29.5 KB

image
image1131×437 15 KB

2
| username: Kongdom | Original post link

It looks like the TOP SQL or performance analysis feature

3
| username: Jellybean | Original post link

You can try disabling SQL statement analysis in the Dashboard interface to see if it improves the situation.

4
| username: zhaokede | Original post link

If you analyze it, pay attention to the logs. To solve it, the reboot method usually works.

5
| username: 哈喽沃德 | Original post link

Check the configuration files of ng-monitoring-server and the monitoring system settings to ensure they are consistent with the recommended settings.
Analyze the monitoring data and logs of ng-monitoring-server to identify the root cause of the specific issue.

6
| username: TiDBer_vZIeuSNY | Original post link

It’s a very scary event when the memory of ng-monitoring-server suddenly spikes. Are there any parameters to limit the memory of ng-monitoring-server?

7
| username: Jasper | Original post link

You can collect flame graphs to take a look.