“No data for 30 minutes.”
Example good log:
Check if your SQL instance uses a non-default port. Update $MSSQL.PORT if necessary.
On the same SQL host, enable:
nodata(/YourHost/perf_instance["SQLServer:Databases(_Total)\Data File(s) Size (KB)",_Total],30m)=1
Start SQL Browser and ensure Windows Firewall allows UDP 1434 inbound.
Problem: MSSQL: Failed to fetch info data (or no data for 30m) zabbix mssql failed to fetch info data -or no data for 30m-
Even if a connection is established, the provided user may lack the necessary permissions to query the required system tables and performance counters. A key symptom here is that some items, such as uptime or version information, might work, while others that require deeper system access (like performance counters) fail. This partial success is a strong clue pointing to a permissions issue.
When Zabbix triggers or "No data for 30m" , the root cause is rarely the same. The former suggests an authentication or query execution failure; the latter suggests timeouts, deadlocks, or connectivity intermittency.
GRANT VIEW SERVER STATE TO zabbix; (or VIEW SERVER PERFORMANCE STATE for SQL 2022). GRANT VIEW ANY DEFINITION TO zabbix; . “No data for 30 minutes
: The monitoring user must have specific rights to view server state and access the . Use the following T-SQL to grant required permissions: GRANT VIEW SERVER STATE TO [zabbix_user] VIEW SERVER PERFORMANCE STATE for SQL 2022+) GRANT VIEW ANY DEFINITION TO [zabbix_user] Read access to msdb.dbo.sysjobs msdb.dbo.sysjobservers msdb.dbo.sysjobactivity Zabbix Git repository ODBC Configuration Issues (ODBC Template) Port Formatting
Open your mssql.conf file and define your connection parameters using named sessions. This prevents you from exposing cleartext passwords across global macros: