Zabbix Mssql Failed To Fetch Info Data -or No Data For 30m- [REAL – 2027]
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:
Ensure you have the Microsoft ODBC Driver (version 17 or 18) installed on the Zabbix server or proxy, as it is required even when using Agent 2.
Look for status = 'suspended' (blocked) or running for hours. zabbix mssql failed to fetch info data -or no data for 30m-
Restart the Zabbix Agent 2 service to apply these changes. Common Troubleshooting Steps
Set TrustServerCertificate=yes or complete the OpenSSL chain trust. Object name parsing issues due to dynamic TCP ports Before diving into the solutions, it's helpful to
To customize the time period or item, the standard expression for a 30-minute "no data" alert looks like this: nodata(/Host/mssql.info_item,30m)=1 If you'd like, I can help you:
First, confirm the foundation is solid. Zabbix monitors MS SQL Server via an ODBC connection, which requires two main components on your Zabbix Server or Zabbix Proxy: Restart the Zabbix Agent 2 service to apply these changes
This comprehensive guide will walk you through the root causes of this error and provide step-by-step solutions to restore your database monitoring. Understanding the Root Cause
Before you do anything in Zabbix, test the connection from the command line. This bypasses Zabbix entirely and isolates driver issues.
Are you using or the ODBC-based template for this monitoring?
The Zabbix monitoring user requires specific permissions to access system views and performance counters. If these are missing, the query that fetches "info data" will fail. Ensure the monitoring user has these permissions: SERVER STATE [zabbix_user]; DEFINITION [zabbix_user]; -- For SQL Agent jobs monitoring: dbo.sysjobs [zabbix_user]; dbo.sysjobactivity [zabbix_user]; dbo.agent_datetime [zabbix_user]; Use code with caution. Copied to clipboard 2. ODBC Driver Configuration (Zabbix Server/Proxy)