The "Failed to fetch info data" or "no data for 30m" error in Zabbix for MSSQL typically indicates a between your Zabbix server/proxy and the SQL instance . 🛠️ Quick Troubleshooting Checklist
Tom pulled up his own tools. "It's up. CPU 12%. Memory fine. Locks… no deadlocks. Connections…" He paused. "Huh. I see the Zabbix proxy connected. But it's just… waiting." zabbix mssql failed to fetch info data -or no data for 30m-
This is a trending/front-end message from the Zabbix UI. It means the server has successfully requested data from the agent, but the value is persistently empty , NULL , or exceeds the zabbix.history sync period. connectivity or permission issue The "Failed to fetch
Zabbix agent (Windows) comes in both 32-bit and 64-bit flavors. The ODBC Driver for SQL Server must match the , not the OS bitness. Check DB credentials & permissions
"action_name": "MSSQL Fetch Failure Alert", "conditions": "trigger_name": "MSSQL: Failed to fetch info data OR no data for 30m", "trigger_severity": ["high", "disaster"] , "operations": "default_subject": "CRITICAL: MSSQL data fetch failed on HOST.NAME", "default_message": "Problem started at EVENT.TIME on EVENT.DATE\n Problem name: TRIGGER.NAME\n Host: HOST.NAME\n Severity: TRIGGER.SEVERITY\n\n Original event ID: EVENT.ID\n Check MSSQL connectivity:\n 1. Verify SQL Server is running\n 2. Check firewall rules\n 3. Validate credentials in Zabbix configuration\n 4. Review SQL error logs\n\n Last 5 fetch attempts: ITEM.VALUE<ms.sql[fetch_data],5>", "recovery_subject": "RECOVERY: MSSQL fetch restored on HOST.NAME", "recovery_message": "Problem resolved at EVENT.RECOVERY.TIME\n Duration: EVENT.DURATION\n Host: HOST.NAME"
She called Tom, the database admin. "Hey, look at your SQL server. Zabbix is blind."