Info Data -or No Data For 30m- - Zabbix Mssql Failed To Fetch

If the script takes 15 seconds to run, but the Zabbix timeout is set to 3 seconds (default), the connection is cut. Zabbix registers this as a failed fetch. If this happens repeatedly, the item goes into a "Not Supported" state for a period (often 10-30 minutes) before retrying, causing the "No data for 30m" gap. Repackme | Best

Subject: Resolving "Failed to fetch info data" and "No data for 30m" errors for Microsoft SQL Server. Audience: System Administrators, DevOps Engineers, DBAs. 1. Executive Summary The Zabbix "Template DB MSSQL" relies heavily on PowerShell scripts and specific ODBC connections to extract performance and availability data. When the Zabbix frontend displays "No data for 30m" or the server log reports "Failed to fetch info data," it indicates a breakdown in the communication chain between the Zabbix Server/Proxy and the MSSQL instance. Gift From Above -2003- Ok.ru [SAFE]

If the error logs suggest "Access Denied" or return null values for metrics.