If using Microsoft ODBC Driver 18 for Linux/Windows, encryption is on by default, leading to certificate failures if not configured correctly.
isql -v MSSQL_DSN zabbix_user 'password' SELECT GETDATE();
If this command fails, it points to a problem with the Zabbix agent configuration. A successful result confirms that your Zabbix server can correctly execute the ODBC query through the agent.
Problem: MSSQL: Failed to fetch info data (or no data for 30m) zabbix mssql failed to fetch info data -or no data for 30m-
-- For SQL Server 2017-2022 CREATE LOGIN zabbix WITH PASSWORD = 'YourSecurePassword'; GRANT VIEW SERVER STATE TO zabbix; -- Use VIEW SERVER PERFORMANCE STATE for 2022+ GRANT VIEW ANY DEFINITION TO zabbix; USE msdb; CREATE USER zabbix FOR LOGIN zabbix; GRANT SELECT ON msdb.dbo.sysjobs TO zabbix; -- Grant additional permissions as needed for Agent monitoring GO Use code with caution. 2. Resolve TLS & Encryption Issues (ODBC Driver 18+)
Problem: MSSQL: Failed to fetch info data (or no data for 30m)
By default, Developer and Express editions of SQL Server do not enable TCP/IP connections, which prevents Zabbix from communicating over the network. If using Microsoft ODBC Driver 18 for Linux/Windows,
Once you correct the permissions or
By following these steps, you should be able to identify whether the issue is a network restriction, a permission issue, or a misconfiguration of the ODBC driver.
Troubleshooting Zabbix MSSQL monitoring issues requires a systematic approach to identify and resolve the underlying causes. By following these steps, you should be able to identify and resolve the issues causing the "failed to fetch info data" or "no data for 30m" errors. Problem: MSSQL: Failed to fetch info data (or
Problem: MSSQL: Failed to fetch info data (or no data for 30m)
Several known issues in specific Zabbix versions can cause this error. Check the Zabbix Jira project for issues matching your version:
mssql.custom.query[Server=.;Trusted_Connection=True;,SELECT cntr_value FROM sys.dm_os_performance_counters WHERE object_name='SQLServer:Buffer Manager' AND counter_name='Buffer cache hit ratio']
This specific error usually originates from the (which has native MSSQL plugin support) or a custom ODBC/UserParameter setup.