Error with Prometheus custom rule_dir

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

Original topic: prometheus自定义rule_dir报错

| username: jaybing926

[TiDB Usage Environment] Production Environment
[TiDB Version]
Cluster version: v5.4.3

[Encountered Problem: Phenomenon and Impact]
Custom Prometheus rule_dir, added configuration rule_dir: /home/tidb/prometheus_rule through edit-config

monitoring_servers:
- host: 192.168.241.71
  ssh_port: 17717
  port: 9090
  ng_port: 12020
  deploy_dir: /home/tidb/deploy/prometheus-9090
  data_dir: /disk2/prometheus-9090
  log_dir: /home/tidb/deploy/prometheus-9090/log
  external_alertmanagers:
  - host: 192.168.241.16
    web_port: 9093
  arch: amd64
  os: linux
  rule_dir: /home/tidb/prometheus_rule

The error when reloading the cluster is as follows:

However, this node does have this directory, and the directory was created by the tidb user with permissions. What is going on here?

[Attachment: Screenshot/Log/Monitoring]

| username: jaybing926 | Original post link

Got it, this directory is on the TiUP management machine.

| username: Fly-bird | Original post link

:100: :100: :100: :100:

| username: oceanzhang | Original post link

Do older versions of monitoring still need to be configured manually?

| username: jaybing926 | Original post link

I don’t quite understand~~
I feel that the default rule metrics of TiDB are too low, and in many cases, they need to be modified manually~~

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.