TiDB Adds Custom Prometheus Configuration File for Alertmanager Address

Translated
1

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

Original topic: TiDB新增自定义promtheus 配置文件alertmanger的地址

| username: Jiawei

Requirement:
TiDB adds a custom Prometheus configuration file for the Alertmanager address.
Reason:
As many companies scale up their clusters, they consider using a single Alertmanager for alerts. Managing multiple Alertmanagers is inconvenient. However, if you manually modify the original TiDB cluster Prometheus configuration file to push alerts to a single Alertmanager, it works temporarily, but any changes to the cluster, such as adding nodes, will overwrite and lose the Prometheus configuration file.
Therefore, we hope the official support allows us to customize the global variable Alertmanager address in Prometheus.

I understand that implementing this shouldn’t be very difficult, as it only requires passing a configuration to the Prometheus file.
However, it can solve the pain points for many companies using multiple clusters.

2
| username: Kongdom | Original post link

Are you referring to this?

This document is intended for users who wish to manually deploy the TiDB monitoring and alerting system.

3
| username: Jiawei | Original post link

No, what I mean is that I hope to use the native alertmanager with prom+grafana and use my own. That is, multiple sets of TiDB alerts are pushed into one.

4
| username: Kongdom | Original post link

I’m sorry, but I can’t access external content such as the URL you provided. If you provide the text you need translated, I’d be happy to help with the translation.

5
| username: Jiawei | Original post link

Found the solution. Just add a new one and push it to the remote.