How to Deploy node_exporter Separately

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

Original topic: 如何单独部署node_exporter

| username: 路在何chu

[TiDB Usage Environment] Production Environment
[TiDB Version]
[Reproduction Path] What operations were performed when the issue occurred
Modified the path of tikv to /data1/tidb/, but node_exporter is still under the /data/tidb directory. Now the /data disk has been unmounted. How to deploy node_exporter separately to /data1? Current configuration:
node_exporter_port: 9100
blackbox_exporter_port: 9115
deploy_dir: /data/tidb/tidb-deploy/monitor-9100
data_dir: /data/tidb/tidb-data/monitor-9100
log_dir: /data/tidb/tidb-deploy/monitor-9100/log
[Encountered Issue: Issue Phenomenon and Impact]
Can a specific IP be set separately? Otherwise, the tikv on that node always reports an error
timed out waiting for port 9115 to be started after 2m0s

| username: 路在何chu | Original post link

One of the TiKV nodes changed its path to /data1, while the other two TiKV nodes are still under /data.

| username: xfworld | Original post link

Refer to this:
【SOP 系列 12】TiUP 修改集群 IP 、Port 和目录 - TiDB 的问答社区

| username: Fly-bird | Original post link

deploy_dir: /data1/

| username: dba远航 | Original post link

Move the original file to /data1, then leave a symbolic link at the original location.

| username: tidb菜鸟一只 | Original post link

I think directly scaling down and then scaling up is more convenient…