“Failed to fetch info data” immediately.
Look for the $MSSQL.TIMEOUT macro in your Zabbix host configurations and increase it to 15 or 20 seconds.
Once permissions and drivers are corrected, Zabbix might still display the error until the 30-minute item interval passes. You can force Zabbix to retry immediately. Go to > Hosts and click on your MSSQL host. Click on Items or Discovery rules . zabbix mssql failed to fetch info data -or no data for 30m-
The error is a common trigger in Zabbix, signaling that the master item responsible for gathering server metrics is failing to retrieve or process information. This generally occurs when using the " MSSQL by ODBC " or "MSSQL by Zabbix agent 2" templates. Core Causes of the "No Data" Alert
The ODBC DSN pointed to SQLCLUSTER01 (virtual name). After failover to node 2, the DSN resolved to the correct IP, but the Zabbix agent on node 2 had a different service account SID that lacked permissions. Failover did not replicate SQL logins. “Failed to fetch info data” immediately
ybcnyc. Junior Member. Joined: Jun 2022. Posts: 1. MSSQL monitoring - MSSQL: Failed to fetch info data (or no data for 30m) 16-06-
MSSQL: Failed to fetch info data (or no data for 30m) - suggestions - ZABBIX Forums You can force Zabbix to retry immediately
If you are using the , data collection relies on a Go-based compiled plugin running natively inside the agent on the target Windows/Linux machine. 1. Fix the Plugin Configuration File Placement
When Zabbix says "failed to fetch info data," it means the agent attempted to execute a query (likely against performance counters or DMVs) and received:
StartAgents=32 Timeout=30 ODBCPoolSize=100 EnableRemoteCommands=1