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

The "No data for 30m" error in MSSQL monitoring is rarely a network outage and almost always a script execution failure. By increasing the parameter to accommodate heavy SQL queries and ensuring PowerShell Execution Policies allow the scripts to run, administrators can restore data flow and maintain visibility into their database infrastructure.

This piece will trigger when:

Create a custom UserParameter that uses the localized name, or switch to the sql.count item using T-SQL queries instead of perfmon. zabbix mssql failed to fetch info data -or no data for 30m-

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'; The "No data for 30m" error in MSSQL

The allowed range is 1-30 seconds; the default is the global Agent 2 timeout. The allowed range is 1-30 seconds