aigarskadikis/zabbix-proxy-sqlite3 repository overview

The following docker container eases up using ODBC monitoring by using ODBC connection string. For example, use item keys in Zabbix:

Oracle:
db.odbc.get["test1",,"Driver=/usr/lib/oracle/19.15/client64/lib/libsqora.so.19.1;DBQ=//192.168.88.32:1521/test;UID=odbc_monitor;PWD=zabbix;"]

Microsoft SQL:
db.odbc.get["test1","","Driver=/opt/microsoft/msodbcsql18/lib64/libmsodbcsql-18.0.so.1.1;Server=192.168.88.32;Database=master;UID=odbc_monitor;PWD=zabbix;TrustServerCertificate=Yes;"]

PostgreSQL:
db.odbc.get["test1",,"Driver=/usr/lib64/psqlodbcw.so;Server=192.168.88.32;Port=5432;Database=postgres;Uid=odbc_monitor;Pwd=zabbix"]

MySQL:
db.odbc.select["test1",,"Driver=/usr/lib64/libmyodbc8w.so;Server=192.168.88.32;Port=3306;Database=zabbix;Uid=odbc_monitor;Pwd=zabbix;"]

Compile profile: https://github.com/aigarskadikis/docker-build/tree/main/zabbix-docker/Dockerfiles/proxy-sqlite3⁠

Known issues: "MS SQL" or "Oracle" monitoring does not work if the DB engine runs also in a container and to reach it must cross multiple NATs. Solution is to kick-start a Zabbix proxy container in the same internal docker network as "MS SQL" or "Oracle" container runs.