Currently ODBC (database monitor) items are executed from the Zabbix Server or the Zabbix Proxy. We would like the Zabbix agent to be able to make the ODBC calls.

There is a use case we have encounted with a database application which is configured at potentially many hundreds of locations and is the only system at that location. Communication between sites is Internet based and not totally private.

The current ODBC item configuration means that if we wanted to take advantage of secure comms between the site and the Zabbix server we would need to:

• Install and maintain a proxy at each site - this is impractical because the database is the only server in use the location so we'd have to have a host definition for the DB server and the proxy and also have to increase the monitoring burden by monitoring the proxy itself.
• If the proxy isn't at the same site as the DB server, then we'd need to open port 1433 (for MSSQL) for it to work which isn't a good thing to do.

If the AGENT could perform the DB Monitor items rather than (or as well as) the server and proxy, this woud increase security and remove the need for user parameters (which is the only current workaround).

Please review.

Regards,

Dave