"MSSQL: Failed to fetch info data (or no data for 30m)" typically indicates a communication or permission breakdown between Zabbix and your SQL Server

MSSQL: Failed to fetch info data (or no data for 30m) - Zabbix

Restart the agent. Also, spread items across multiple items or use a Zabbix proxy for distributed SQL monitoring.

nodata(/YourHost/perf_instance["SQLServer:Databases(_Total)\Data File(s) Size (KB)",_Total],30m)=1

MSSQL: Failed to fetch info data (or no data for 30m) - Zabbix

Zabbix’s ODBC DSN often uses Server=localhost\INSTANCE . This requires SQL Browser (UDP port 1434) to resolve the dynamic port. If SQL Browser is disabled, the connection hangs then fails.

This often indicates:

Problem: MSSQL: Failed to fetch info data (or no data for 30m)

Zabbix templates scan SQL Server Agent jobs to monitor backup and automation tasks. Grant explicit read permissions inside the msdb database:

Before diving into the troubleshooting steps, it's essential to understand the possible causes of these errors:

MSSQL: Failed to fetch info data (or no data for 30m) - Zabbix

Seeing the "" error or getting a " No data for 30m " alert on your Zabbix dashboard is a common headache for database administrators and DevOps engineers. This issue typically means the Zabbix agent or proxy cannot communicate with your Microsoft SQL Server instance, or the execution of the monitoring script is timing out.