Ad Widget

Collapse

ODBC query monitoring

Collapse
This topic has been answered.
X
X
 
  • Time
  • Show
Clear All
new posts
  • kyus
    Senior Member
    • Feb 2024
    • 172

    #1

    ODBC query monitoring

    Hey everyone!

    So, i'm trying to monitor some queries in PostgreSQL using ODBC, it worked on a Debian server with a Proxy running directly on it.
    Now, i'm facing issues to make it work with a Proxy running in a docker container in a CentOS 7 VM.

    I've did some testing, and it seems like Zabbix looks for the odbc.ini and odbcinst.ini files in the proxy container.
    Is there a way to tell Zabbix to look for the files somewhere else? Or should i try to compile the proxy container with ODBC libraries and mount volumes for both files?
    Not sure about how to proceed, since i'm fairly new to docker.

    Server, Proxy and Agent are all running in version 6.0.x
  • Answer selected by kyus at 08-04-2024, 20:36.
    kyus
    Senior Member
    • Feb 2024
    • 172

    Well, yes, the proxy/server looks for the file where it is installed, so, in this case, it was looking for the file in the container where the proxy was running and that's what was causing the errors.

    To test it, I've mounted the odbc.ini and odbcinst.ini files and installed the packages "unixodbc" and "odbc-postgresql" in the container, doing so fixed the errors and the monitoring started to work as expected.

    Comment


    • kyus
      kyus commented
      Editing a comment
      The item type i used is "Database Monitor", you don't need agent installed to use it, that's probably the reason why it looks for the file in the container.
  • kyus
    Senior Member
    • Feb 2024
    • 172

    #2
    Well, yes, the proxy/server looks for the file where it is installed, so, in this case, it was looking for the file in the container where the proxy was running and that's what was causing the errors.

    To test it, I've mounted the odbc.ini and odbcinst.ini files and installed the packages "unixodbc" and "odbc-postgresql" in the container, doing so fixed the errors and the monitoring started to work as expected.

    Comment


    • kyus
      kyus commented
      Editing a comment
      The item type i used is "Database Monitor", you don't need agent installed to use it, that's probably the reason why it looks for the file in the container.
Working...