The webhook file added to alertmanager.yml is overwritten by tiup cluster reload

Translated
1

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

Original topic: alertmanager.yml增加webhook文件被覆盖tiup cluster reload

| username: daihu

【TiDB Environment】Test Environment
【TiDB Version】v5.4.0
【Encountered Issue】
The tiup cluster reload command overwrites the alertmanager.yml file, causing the previously configured webhook to be lost. How can this issue be avoided or resolved?
【Reproduction Steps】What operations were performed that led to the issue
【Issue Phenomenon and Impact】
How to avoid such issues

2
| username: ddhe9527 | Original post link

To configure in the cluster topology file.

3
| username: daihu | Original post link

Currently, the configuration only supports modifying the listening address, nothing else.

4
| username: yilong | Original post link

Do you know where the alerts need to be sent? For example, can you configure wechat_config as referenced in this post?

5
| username: weixiaobing | Original post link

You can refer to 通过 TiUP 部署 TiDB 集群的拓扑文件配置 | PingCAP 文档中心

  • config_file: This field specifies a local file that will be transferred to the target machine during the cluster configuration initialization phase as the configuration for Alertmanager.