You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm really pushed to the wall, it's driving me crazy.
Troubleshooting Steps:
In the Prometheus backend, the node is online, and Targets can be seen.
Upon clicking in, it returns around 2000 data points.
Adding scrape_interval: 5m, scrape_timeout: 1m in Prometheus configuration allows a small portion of data to appear, but the error in mysqld_exporter persists.
Service restarts are ineffective, as are server restarts.
mysqld_exporter
Prometheus
Grafana
/metrics data can be obtained, tested with curl http://10.0.0.9:9104/metrics
On the server, it can be obtained.
On the mysqld_exporter local machine, it can be obtained.
The data volume is normal with around 2000 metrics.
The response time takes several seconds.
The mysqld_exporter service configuration file .my.cnf is correct.
The same configuration works on other servers.
Increasing the timeout with connect_timeout=10 is ineffective.
Changing the local address to host=localhost is ineffective.
The database account is correct.
Remote tools test the account with no issues.
The account has % privileges as well as local privileges.
Creating a new account with root privileges does not resolve the issue.
The account password does not contain special characters such as #.
The server can Ping the client machine, and the firewalls are all disabled.
The port is normal, port number 9104, not occupied.
The problematic client and the non-problematic client have the same version, both are go1.21.5.
The text was updated successfully, but these errors were encountered:
when i call curl http://myhost:9104/metrics | less at the db host, i got immediately a response... when i call curl http://myhost:9104/metrics?target=myhost:9104 | less (like Prometheus) the call does not come to an end.
--log.level=debug doesn't write out more then "level=error msg="Error pinging mysqld" err="context canceled""
Ports are open, checked it with sudo netstat -tulpn | grep LISTEN | grep exporter
connecting mysql --defaults-file=/my/config/is/here.cnf works fine
Exporter is started via: /opt/mysql/product/exporters/mysqld_exporter --config.my-cnf=/my/config/is/here.cnf --web.listen-address=:9104 --log.level=debug
I'm really pushed to the wall, it's driving me crazy.
Troubleshooting Steps:
Prometheus
backend, the node is online, andTargets
can be seen.scrape_interval: 5m
,scrape_timeout: 1m
inPrometheus
configuration allows a small portion of data to appear, but the error inmysqld_exporter
persists.mysqld_exporter
Prometheus
Grafana
/metrics
data can be obtained, tested withcurl http://10.0.0.9:9104/metrics
mysqld_exporter
local machine, it can be obtained.mysqld_exporter
service configuration file.my.cnf
is correct.connect_timeout=10
is ineffective.host=localhost
is ineffective.%
privileges as well aslocal
privileges.#
.Ping
the client machine, and the firewalls are all disabled.go1.21.5
.The text was updated successfully, but these errors were encountered: