Sergei Zyubin

Hi @dtoxin7 ! I'm interested in your problem, as I've experienced something similar in the past. If you have time, please take a look at the fork here: https://github.com/burningalchemist/sql_exporter. I've...

@jesus-velez It's mainly code related, but it's also reflected in the settings. :) It really depends on how a driver interacts with your database instance (and what are the quirks),...

@jesus-velez Glad to hear it works for you! 👍

@free This issue can be closed. I've recently worked on that and found out how to resolve the problem for CrateDB with additional libpq parameters. Meanwhile, I have also applied...

Hi @JoostvdB94, you might want to look at the fork I maintain: https://github.com/burningalchemist/sql_exporter It's compatible, and I keep track on the security and dependency updates with minor changes. 👍

@nssiwi It is likely a configuration issue. Could you provide more details if it's possible? 🙂

@debanitaghosh `sql-exporter.yml` by default is expected to be next to the executable, not in `documentation` folder. As an alternative, you can specify location with `-config.file` parameter. Let me know if...

Hey @paarth1995, please check my message. You need to copy `sql_exporter.yml` from the documentation folder to the place where the executable resides. Otherwise, use `-config.file` parameter to provide the config...

Hi, if you're working with Kubernetes, you can to provide the config files via the ConfigMap object, mount it to the path where sql_exporter resides. Otherwise you can mount it...

@rashmi-kj According to the Dockerfile [1] the only present thing in the image is the binary. The rest should be attached from the user side. Please take a look at...