If the server requires encryption, a self-signed certificate can cause the connection to fail unless TrustServerCertificate is specified. Troubleshooting Steps
The most common reason for a "failed to fetch" error is that the monitoring agent cannot reach the SQL Server port. mssql: failed to fetch info data (or no data for 30m)
| Category | Specific Cause | |----------|----------------| | | Network firewall dropping long‑living connections; DNS resolution issues; Azure SQL Gateway timeout. | | Query Performance | Blocking queries, deadlocks, or an inefficient sys.dm_os_performance_counters query that exceeds 30 min. | | Resource Exhaustion | TempDB full, transaction log full, or memory pressure stalling system DMV responses. | | Monitoring Agent Behavior | Hardcoded 30‑min socket timeout; missing retry logic; synchronous fetch from a busy sys.dm_exec_requests . | | SQL Server Configuration | remote query timeout set to 0 (unlimited) causing indefinite wait; query wait high. | | External Dependencies | Anti‑virus scanning .mdf/.ldf files; backup job holding shared locks on system tables. | If the server requires encryption, a self-signed certificate
MSSQL: Failed to fetch info data (or no data for 30m) - Zabbix Comment * Joined: Nov 2020. * Posts: 7. | | Query Performance | Blocking queries, deadlocks,
On Linux-based monitoring agents, the ODBC Driver for SQL Server and mssql-tools must be correctly installed to execute remote queries.