MSSQL: Failed to fetch info data (or no data for 30m) - Zabbix
: If you can connect via sqlcmd but not Zabbix, you may need to specify TrustServerCertificate=Yes in your odbc.ini file or ensure the Microsoft ODBC Driver 18 is properly handling encryption. Database Permissions
You can use the following text for your trigger name or notification body: zabbix mssql failed to fetch info data -or no data for 30m-
The most frequent cause is a simple credential mismatch. Ensure your Host Macros are correctly set: : The SQL login name. $MSSQL.PASSWORD : The corresponding password.
If you are monitoring Microsoft SQL Server (MSSQL) using Zabbix, encountering the trigger is a common scenario. This error, often associated with the MSSQL by ODBC or MSSQL by Zabbix agent 2 templates, indicates that the Zabbix server or proxy hasn't received valid performance data from the SQL instance for a prolonged period. MSSQL: Failed to fetch info data (or no
recovery_expression: | last(/MSSQL_Template/ms.sql.fetch_success)=1 and min(/MSSQL_Template/ms.sql.fetch_success, 5m)=1
Tom pulled up his own tools. "It's up. CPU 12%. Memory fine. Locks… no deadlocks. Connections…" He paused. "Huh. I see the Zabbix proxy connected. But it's just… waiting." $MSSQL
ybcnyc. Junior Member. Joined: Jun 2022. Posts: 1. MSSQL monitoring - MSSQL: Failed to fetch info data (or no data for 30m) 16-06-
When the Zabbix MSSQL by ODBC or MSSQL by Zabbix agent template is used, Zabbix expects regular check-ins (e.g., every 5 minutes). If the server returns empty data, crashes, or times out, the nodata() function in Zabbix triggers this alert after 30 minutes of silence. Incorrect ODBC credentials or permissions.