The Zabbix monitoring user requires specific granular permissions to view system dynamic management views (DMVs) and performance counters. Without these, queries targeting master tables fail instantly. Step 1: Verify Server-Level Permissions
The errors βFailed to fetch info dataβ and βNo data for 30mβ are not Zabbix bugs β they are symptoms of a broken contract between your monitoring tool and your database. By systematically checking ODBC drivers, service account permissions, instance names, and localization, you can restore full visibility.
isql -v <DSN> <USERNAME> <PASSWORD>
$keys = @( "perf_instance[\MSSQLSERVER,'SQLServer:General Statistics','User Connections']", "perf_instance[\MSSQLSERVER,'SQLServer:Buffer Manager','Page life expectancy']" ) foreach ($key in $keys) & "C:\Program Files\Zabbix Agent\zabbix_get.exe" -s 127.0.0.1 -k $key
Look for an entry like ODBC Driver 18 for SQL Server or similar. If missing, install the msodbcsql package from Microsoft. zabbix mssql failed to fetch info data -or no data for 30m-
Switch to sys.dm_db_resource_stats or sys.server_resource_stats views. Customize the user parameter to query these instead. The official Zabbix template for Azure SQL Database is different from on-prem MSSQL.
Locate your zabbix_agent2.conf file.
Example bad log: