Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: Blackbox_exporter_server_is_down
What is the cause of this exception? Is it due to a monitor malfunction?
Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: Blackbox_exporter_server_is_down
What is the cause of this exception? Is it due to a monitor malfunction?
Log in to the corresponding server and check the blackbox_exporter process. Each instance should have a corresponding process.
It should be an issue with the alertmanager.conf configuration, but I don’t know why this configuration file of alertmanager always gets reset. I clearly configured DingTalk alerts, but after a while, I find it reset.
Reset the configuration file? That shouldn’t be the case.
It shouldn’t happen… but it does. It occurs in both the testing and production environments, so I’ve backed up this file locally.
How did you configure the configuration file?
What operations did you perform before and after the configuration?
It shouldn’t be a version issue, whether it’s TiDB or DM. Previously, DM used v2.x, and now using v5.2.0 and v5.4.0, this problem still occurs. We just added a DingTalk alert, killed the alertmanager process after modifying the configuration, and it would restart automatically. It doesn’t immediately change the file, and the alert is fine. It’s just that after a long time, when we check the file, we find that the file has been reset.
It might be related to your operation, the configuration was not truly persisted.