部署了dm以后看不到dm的监控

Starting component `cluster`: /tidb/app/.tiup/components/cluster/v1.6.0/tiup-cluster display tidb-join
Cluster type:       tidb
Cluster name:       tidb-join
Cluster version:    v5.2.1
Deploy user:        tidb
SSH type:           builtin
Dashboard URL:      http://10.3.87.30:2379/dashboard
ID                Role          Host        Ports                            OS/Arch       Status   Data Dir                           Deploy Dir
--                ----          ----        -----                            -------       ------   --------                           ----------
10.3.87.36:9093   alertmanager  10.3.87.36  9093/9094                        linux/x86_64  Up       /tidb/tidb-data/alertmanager-9093  /tidb/app/alertmanager-9093
10.3.87.30:8300   cdc           10.3.87.30  8300                             linux/x86_64  Up       /tidb/tidb-data/cdc-8300           /tidb/app/cdc-8300
10.3.87.31:8300   cdc           10.3.87.31  8300                             linux/x86_64  Up       /tidb/tidb-data/cdc-8300           /tidb/app/cdc-8300
10.3.87.32:8300   cdc           10.3.87.32  8300                             linux/x86_64  Up       /tidb/tidb-data/cdc-8300           /tidb/app/cdc-8300
10.3.87.36:3000   grafana       10.3.87.36  3000                             linux/x86_64  Up       -                                  /tidb/app/grafana-3000
10.3.87.30:2379   pd            10.3.87.30  2379/2380                        linux/x86_64  Up|L|UI  /tidb/tidb-data/pd-2379            /tidb/app/pd-2379
10.3.87.31:2379   pd            10.3.87.31  2379/2380                        linux/x86_64  Up       /tidb/tidb-data/pd-2379            /tidb/app/pd-2379
10.3.87.32:2379   pd            10.3.87.32  2379/2380                        linux/x86_64  Up       /tidb/tidb-data/pd-2379            /tidb/app/pd-2379
10.3.87.36:9090   prometheus    10.3.87.36  9090                             linux/x86_64  Up       /tidb/tidb-data/prometheus-9090    /tidb/app/prometheus-9090
10.3.87.30:4000   tidb          10.3.87.30  4000/10080                       linux/x86_64  Up       -                                  /tidb/app/tidb-4000
10.3.87.31:4000   tidb          10.3.87.31  4000/10080                       linux/x86_64  Up       -                                  /tidb/app/tidb-4000
10.3.87.32:4000   tidb          10.3.87.32  4000/10080                       linux/x86_64  Up       -                                  /tidb/app/tidb-4000
10.3.87.30:9000   tiflash       10.3.87.30  9000/8123/3930/20170/20292/8234  linux/x86_64  Up       /tidb/tidb-data/tiflash-9000       /tidb/app/tiflash-9000
10.3.87.31:9000   tiflash       10.3.87.31  9000/8123/3930/20170/20292/8234  linux/x86_64  Up       /tidb/tidb-data/tiflash-9000       /tidb/app/tiflash-9000
10.3.87.32:9000   tiflash       10.3.87.32  9000/8123/3930/20170/20292/8234  linux/x86_64  Up       /tidb/tidb-data/tiflash-9000       /tidb/app/tiflash-9000
10.3.87.30:20160  tikv          10.3.87.30  20160/20180                      linux/x86_64  Up       /tidb/tidb-data/tikv-20160         /tidb/app/tikv-20160
10.3.87.31:20160  tikv          10.3.87.31  20160/20180                      linux/x86_64  Up       /tidb/tidb-data/tikv-20160         /tidb/app/tikv-20160
10.3.87.32:20160  tikv          10.3.87.32  20160/20180                      linux/x86_64  Up       /tidb/tidb-data/tikv-20160         /tidb/app/tikv-20160
Total nodes: 18


10.3.87.36:9093  alertmanager  10.3.87.36  9093/9094  linux/x86_64  Up         /tidb/app/dm/data/alertmanager-9093  /tidb/app/dm/deploy/alertmanager-9093
10.3.87.30:8261  dm-master     10.3.87.30  8261/8291  linux/x86_64  Healthy    /tidb/app/dm/data/dm-master-8261     /tidb/app/dm/deploy/dm-master-8261
10.3.87.31:8261  dm-master     10.3.87.31  8261/8291  linux/x86_64  Healthy    /tidb/app/dm/data/dm-master-8261     /tidb/app/dm/deploy/dm-master-8261
10.3.87.32:8261  dm-master     10.3.87.32  8261/8291  linux/x86_64  Healthy|L  /tidb/app/dm/data/dm-master-8261     /tidb/app/dm/deploy/dm-master-8261
10.3.87.30:8262  dm-worker     10.3.87.30  8262       linux/x86_64  Free       /tidb/app/dm/data/dm-worker-8262     /tidb/app/dm/deploy/dm-worker-8262
10.3.87.31:8262  dm-worker     10.3.87.31  8262       linux/x86_64  Free       /tidb/app/dm/data/dm-worker-8262     /tidb/app/dm/deploy/dm-worker-8262
10.3.87.32:8262  dm-worker     10.3.87.32  8262       linux/x86_64  Free       /tidb/app/dm/data/dm-worker-8262     /tidb/app/dm/deploy/dm-worker-8262
10.3.87.36:3000  grafana       10.3.87.36  3000       linux/x86_64  Up         -                                    /tidb/app/dm/deploy/grafana-3000
10.3.87.36:9090  prometheus    10.3.87.36  9090       linux/x86_64  Up         /tidb/app/dm/data/prometheus-9090    /tidb/app/dm/deploy/prometheus-9090
Total nodes: 9

我是从4.0.6升级到5.2.1的
升级成功以后我就去部署了一下dm,面部署成功以后我发现节点配置有点问题,所我就是destroy了一下,然后重新部署,主要是将了一下grafana_servers和alertmanager_servers换到和tidb的grafana_servers和alertmanager_servers到同一个机器上(先前这两个服务IP写错了)

现在我还没有创建同步任务。

我在grafana看不到DM-task这个监控是不是正常的?
如果不正常我该在那里找问题

TiDB的监控和DM的监控是独立的,你现在部署在相同的host和端口下,DM监控应该是没部署成功的。把DM的alertmanager、grafana、prometheus端口修改下,和TiDB集群的区分开。

我重新部署了一下。现在发现tidb的监控的信息被覆盖了。现在只有dm的监控了。我该怎么找回原来的信息啊

此话题已在最后回复的 1 分钟后被自动关闭。不再允许新回复。