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

: This file defines Data Source Names (DSNs), which are aliases for connection settings. Add your DSN definition:

Remember: Use the diagnostics in this guide to enforce a 15-minute maximum data outage, and set up proactive alerts for the monitoring system itself.

Before diving into the solutions, it's helpful to categorize the problem. The error typically falls into one of the following areas, each with distinct symptoms:

Zabbix’s ODBC DSN often uses Server=localhost\INSTANCE . This requires SQL Browser (UDP port 1434) to resolve the dynamic port. If SQL Browser is disabled, the connection hangs then fails. zabbix mssql failed to fetch info data -or no data for 30m-

The Zabbix server, proxy, or agent logs will provide the specific reason for the failure.

Problem: MSSQL: Failed to fetch info data (or no data for 30m)

What do you see when testing the connection via isql or the Zabbix "Test" item button? Share public link : This file defines Data Source Names (DSNs),

Trigger on nodata(5m) for a known always-increasing counter like system.uptime . If uptime stops reporting, your whole SQL monitoring is dead.

This piece will trigger when:

Before diving into logs and permissions, verify the basics. The error typically falls into one of the

odbc: SQLExecDirect: retcode=-1 (42S02: [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Invalid object name 'sys.dm_os_performance_counters'.)

Test if the Zabbix server/proxy can actually reach the database using isql from the command line:

The "Failed to fetch info data" error typically originates from the or MSSQL by DB for Windows templates. It indicates that the Zabbix agent or proxy successfully initiated a connection to the server port, but failed to execute the internal discovery queries or retrieve performance counter data. The most common reasons for this failure include:

Example:

If everything is configured correctly, you should see a Connected! message followed by an SQL> prompt. If you see an error, it's usually a configuration or driver issue. Additionally, test the connection using a simple query to ensure you can fetch data: