Zabbix Mssql Failed To Fetch Info Data -or No Data For 30m- Fixed | Legit

She wrote in her post-mortem: "Zabbix did not lose the data. We lost the ability to fetch it. The silence was the alarm."

<!-- Item with last value tracking --> <item name="MSSQL: Last successful fetch" key="msql.last.success.time"> <type>Zabbix agent</type> <key>perf.mssql[last_success]</key> <value_type>Numeric (unsigned)</value_type> <units>unixtime</units> <delay>60s</delay> </item>

Run this script on your SQL Server to ensure the Zabbix user has the minimum required access: zabbix mssql failed to fetch info data -or no data for 30m-

The error message typically indicates a communication failure between the Zabbix agent/server and the target SQL Server instance . This usually results from incorrect connection settings, missing ODBC drivers, or insufficient database permissions. Immediate Troubleshooting Steps

This is the most critical step. The generic "failed to fetch info" message on the frontend is usually hiding a specific error in the agent log. She wrote in her post-mortem: "Zabbix did not lose the data

Azure SQL Managed Instance does not support sys.dm_os_performance_counters – it raises “Invalid object name”.

MSSQL: Failed to fetch info data (or no data for 30m) - Zabbix Azure SQL Managed Instance does not support sys

Or better (Windows):