Here is a breakdown of why this happens and how to troubleshoot it, categorized by the most common causes.
To resolve the "Failed to fetch" alert, follow these systematic checks: 1. Verify Connectivity
This issue typically stems from connectivity, configuration, or authentication problems between the monitoring agent and the SQL Server: mssql: failed to fetch info data (or no data for 30m)
If SQL counters are missing, you may need to reload them using the lodctr /R command in an elevated prompt. 4. Troubleshoot ODBC & Drivers If you are using an ODBC-based template:
If this fails, check if the SQL Server Browser service is running and ensure TCP/IP is enabled in SQL Server Configuration Manager. 2. Audit Permissions Here is a breakdown of why this happens
If using , verify that the mssql.conf plugin file is correctly configured and included in the main agent configuration. Check for these specific macros in the Zabbix frontend:
Firewalls or network security groups may be blocking the connection on port 1433 or other custom ports. Audit Permissions If using , verify that the mssql
Test the connection manually from the server running the monitoring agent using sqlcmd or a similar tool:
The user account used for monitoring must have the authority to view server-level metadata. Ensure the user has been granted: GRANT VIEW SERVER STATE TO [zabbix_user]; GRANT VIEW ANY DEFINITION TO [zabbix_user]; 3. Review Agent Configuration