Open 0xErnie opened 3 years ago
I decided to switch to the fork burningalchemist/sql_exporter which has updated multiple dependencies.
I am experiencing the same problem with the sql_exporter, where the exporter needs to be restarted in case of network connection problems to the database. Anybody has a working solution for this problem?
Still suffering from the same issue. The exporter is not recovering from DB connectivity problems. Anybody has an idea on how to resolve?
I0513 23:50:20.063691 1 promhttp.go:38] Error gathering metrics: [from Gatherer #1] bad connection I0513 23:51:20.061513 1 promhttp.go:38] Error gathering metrics: [from Gatherer #1] bad connection I0513 23:52:20.062154 1 promhttp.go:38] Error gathering metrics: [from Gatherer #1] bad connection I0513 23:53:20.064057 1 promhttp.go:38] Error gathering metrics: [from Gatherer #1] bad connection I0513 23:54:20.063563 1 promhttp.go:38] Error gathering metrics: [from Gatherer #1] bad connection
@rgardelein Have you tried my solution?
Hello 0xErnie, Thank you for your reply. I have not tried your solution by switching to the burningalchemist/sql_exporter. Is this solution fully upward compatible? What is your experience with it? rgardelein
Even if the MySQL database is available again, the exporter still indicates that the database would be offline. Restarting the exporter solves the problem.
Our configuration: