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

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

Then from (as the Zabbix agent service account):

If this returns zero rows for the user NT SERVICE\ZabbixAgent , you’ve hit the jackpot.

<!-- Item to track fetch failures --> <item name="MSSQL: Info fetch status" key="mssql.info.fetch.status"> <type>Zabbix agent</type> <key>perf.ms sql[fetch.status]</key> <value_type>Numeric (unsigned)</value_type> <units>status</units> <delay>60s</delay> <description>1 = fetch failed, 0 = fetch successful</description> </item>

: If using a named instance, ensure the macro $MSSQL.INSTANCE is set correctly (e.g., MSSQL$InstanceName ). For default instances, this macro should remain unchanged.

Double-click , go to the IP Addresses tab, scroll down to IPAll , and ensure the TCP Port is set to 1433 . Restart the SQL Server Service for changes to take effect. 4. Adjust Timeout Settings

from the command line on the Zabbix server/agent host to verify that the connection works outside of Zabbix. Check Zabbix Logs : Look at the Zabbix Server or Agent log files (usually in /var/log/zabbix/

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

SELECT DISTINCT object_name FROM sys.dm_os_performance_counters;

If you are using the , data collection relies on a Go-based compiled plugin running natively inside the agent on the target Windows/Linux machine. 1. Fix the Plugin Configuration File Placement

“Failed to fetch info data from database.”