: If you are using the MSSQL by Zabbix agent 2 template, ensure the plugin configuration file ( mssql.conf ) is in the correct directory (typically zabbix_agent2.d/plugins.d/ ) and that the agent has been restarted. Common Fixes from the Community
The monitoring user must have specific rights to query system views like sys.dm_os_performance_counters . Without VIEW SERVER STATE (or VIEW SERVER PERFORMANCE STATE for SQL 2022+), the "Get Info" queries return empty results.
Use this checklist to systematically eliminate the error:
If this alert is active, check the following common causes identified by users in the Zabbix Community Forums : zabbix mssql failed to fetch info data -or no data for 30m-
Restart the Zabbix Agent 2 service.
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.
Your_Template:mssql.info.fetch.fail.min(30m)=1 or Your_Template:mssql.info.fetch.data.nodata(30m)=1 : If you are using the MSSQL by
: If you recently upgraded to ODBC Driver 18, it forces encryption by default. If your SQL Server uses a self-signed certificate, you must add TrustServerCertificate=yes to your connection string or the file. Some users found reverting to ODBC Driver 17
zabbix_agent2 -t mssql.info.data["sqlserver://127.0.0.1:1433","zabbix_user","password"] Use code with caution.
Open /etc/zabbix/zabbix_agent2.conf (Linux) or zabbix_agent2.conf (Windows) and update the timeout: Timeout=15 Use code with caution. Use this checklist to systematically eliminate the error:
If you continue to face issues after these steps, it is recommended to review the in the frontend to get specific error codes regarding the failed to fetch message.
Set the global plugin timeout using: