Zabbix Mssql Failed To Fetch Info Data -or No Data For 30m-
This is a trending/front-end message from the Zabbix UI. It means the server has successfully requested data from the agent, but the value is persistently empty , NULL , or exceeds the zabbix.history sync period.
Adjust the trigger expression. Replace nodata(30m) with nodata(30m) and last()<>0 or simply increase the threshold for low-traffic servers. zabbix mssql failed to fetch info data -or no data for 30m-
On the same SQL host, enable:
SELECT session_id, login_name, status, last_request_start_time, last_request_end_time, text FROM sys.dm_exec_sessions s OUTER APPLY sys.dm_exec_sql_text(most_recent_sql_handle) t WHERE login_name = 'zabbix_user'; This is a trending/front-end message from the Zabbix UI
: The DSN name in your Zabbix macro $MSSQL.DSN must exactly match the header in your odbc.ini file. The generic "failed to fetch info" message on
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.
: GRANT VIEW SERVER STATE (or VIEW SERVER PERFORMANCE STATE for 2022+), VIEW ANY DEFINITION , and specific SELECT and EXECUTE rights on msdb objects. Zabbix Backend Configuration
