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

[ Zabbix Server / Proxy ] │ ▼ (Connection Attempt) ┌────────────────────────────────────────────────────────┐ │ Common Failure Points: │ │ 1. Missing View Server State Permissions │ │ 2. Broken FreeTDS/unixODBC Driver Strings │ │ 3. TLS / Self-Signed Certificate Rejections │ │ 4. Agent 2 mssql.conf Plugin Misplacement │ └────────────────────────────────────────────────────────┘ │ ▼ [ Target MSSQL Database ] ──❌ Data Flow Blocked Method 1: Troubleshooting ODBC Monitored Environments

When Zabbix throws this alert, the master item responsible for collecting the bulk of your MSSQL data (often an ODBC query or an Agent 2 plugin call) is failing. Because all other individual metrics depend on this master item, the entire database dataset goes blank, triggering the 30-minute time-out alert. zabbix mssql failed to fetch info data -or no data for 30m-

This is often the root cause. Zabbix cannot establish a connection to the MS SQL Server at all. Symptoms may include a complete absence of data for all items related to the template, errors in Zabbix logs indicating a failed connection, or a ZBX_NOTSUPPORTED status for items like mssql.ping . A common manifestation is the Data source name not found error, indicating that the DSN (Data Source Name) configured in Zabbix is not recognized by the system. [ Zabbix Server / Proxy ] │ ▼

UserParameter=mssql.connections,echo "SELECT cntr_value FROM sys.dm_os_performance_counters WHERE object_name='SQLServer:General Statistics' AND counter_name='User Connections'" | tsql -S localhost -U zabbix -P pass -D master -o /tmp/out -q TLS / Self-Signed Certificate Rejections │ │ 4