This text is structured for an engineer or administrator to diagnose and resolve the root cause. 1. The Core Problem When Zabbix reports “Failed to fetch info data” or “No data for 30m” for an MSSQL template (e.g., Template DB MSSQL by ODBC or Template DB MSSQL by Zabbix Agent 2 ), it indicates a breakdown in the monitoring chain.
[ODBC] Trace = Yes TraceFile = /tmp/odbc_trace.log Reproduce the error and grep for SQLExecDirect . You will see the exact SQL statement that fails and the native SQL error code. Run on the target SQL Server: zabbix mssql failed to fetch info data -or no data for 30m-
failed to fetch info data from [MSSQL item key] ODBC error: [unixODBC][Driver Manager]Data source name not found No data for 30 minutes, rescheduling query Filter logs for ODBC or mssql at debug level ( DebugLevel=4 in zabbix_server.conf ). Step 2 – Test ODBC Connection Manually On the Zabbix server/proxy, run: This text is structured for an engineer or