How to Handle DM Installation Overriding Cluster Monitoring

Translated
1

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

Original topic: 装dm顶掉了cluser监控怎么处理

| username: zhanggame1

[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version]
There was an original TiDB cluster as follows:

image
image1378×458 125 KB

Later, a DM cluster was deployed

image
image1288×282 63.9 KB

The monitoring Prometheus and Grafana were deployed using the same IP and port.
Now the cluster monitoring is gone. Can it be restored?

image
image1123×529 23.9 KB

2
| username: WalterWj | Original post link

Shrink the monitoring for DM. Also forcibly shrink the monitoring for the cluster. Then expand it. Remember to change the machine.

3
| username: redgame | Original post link

I’ll try the expert’s method and see if this phenomenon still occurs.

4
| username: zhanggame1 | Original post link

Tested it, and it can indeed be resolved by scaling down the monitoring and then scaling it up again.

5
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.