When Zabbix fails to fetch MSSQL info data for 30 minutes, it typically indicates a configuration gap between the Zabbix Agent 2 and the MSSQL plugin. Key Solution: Configure MSSQL Plugin Sessions
The most effective way to resolve this "no data" error is to use Named Sessions in your configuration. This bypasses common connection issues by explicitly defining the URI and credentials in the plugin configuration.
Locate the Plugin Config: Open mssql.conf, typically found in /etc/zabbix/zabbix_agent2.d/plugins.d/ (Linux) or the agent's install directory (Windows).
Add a Session: Define a session name (e.g., SQLServer1) and its connection details:
Plugins.MSSQL.Sessions.SQLServer1.Uri=sqlserver:// Plugins.MSSQL.Sessions.SQLServer1.User=zbx_monitor Plugins.MSSQL.Sessions.SQLServer1.Password=
Update Zabbix Frontend: On your MSSQL Host in the Zabbix UI, update the following Macros: $MSSQL.USER: zbx_monitor $MSSQL.PASSWORD:
$MSSQL.DSN: SQLServer1 (matching the session name in your config).
Restart Agent: Restart the Zabbix Agent 2 service to apply these changes. Common Troubleshooting Steps zabbix mssql failed to fetch info data -or no data for 30m-
ODBC Driver Requirements: 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.
Permissions: The monitoring user must have VIEW SERVER STATE (for SQL 2017/2019) or VIEW SERVER PERFORMANCE STATE (for SQL 2022).
Check the Queue: Navigate to Administration > Queue > Queue Details in the Web UI. This shows exactly which items are delayed and for how long, helping you identify if the issue is a single item or the entire plugin. Microsoft SQL monitoring and integration with Zabbix
The errors “Failed to fetch info data” and “No data for 30m” are not Zabbix bugs – they are symptoms of a broken contract between your monitoring tool and your database. By systematically checking ODBC drivers, service account permissions, instance names, and localization, you can restore full visibility.
Remember: No data is never acceptable for a production SQL Server. Use the diagnostics in this guide to enforce a 15-minute maximum data outage, and set up proactive alerts for the monitoring system itself.
After fixing the issue once, document the exact DSN, login permissions, and UserParameter overrides in your runbook. The next time SQL Server patches or a failover occurs, you’ll recover in minutes – not days.
Further Resources
Last updated: For Zabbix 6.4+ and SQL Server 2017-2022.
The error "MSSQL: Failed to fetch info data (or no data for 30m)" in Zabbix typically indicates a breakdown in communication between the Zabbix monitoring component (Server, Proxy, or Agent 2) and the Microsoft SQL Server instance. This alert triggers when the primary "Get status" item, which populates dependent items with JSON data, returns an empty value or fails to execute. 1. Resolve Authentication and Permissions
The most common cause is the monitoring user lacking sufficient rights to view system performance metrics.
MSSQL: Failed to fetch info data (or no data for 30m) - Zabbix
MSSQL: Failed to fetch info data (or no data for 30m) - suggestions * Posts. * Latest Activity. * Photos.
MSSQL: Failed to fetch info data (or no data for 30m) - ZABBIX Forums
Introduction
Zabbix is a popular monitoring tool used to track the performance and health of various systems, including Microsoft SQL Server (MSSQL) databases. However, sometimes Zabbix may encounter issues while monitoring MSSQL databases, resulting in errors such as "failed to fetch info data" or "no data for 30m". This guide aims to provide a step-by-step approach to troubleshooting these issues.
Possible Causes
Before diving into the troubleshooting steps, it's essential to understand the possible causes of these errors:
Troubleshooting Steps
| Error Message | Zabbix Interpretation | Typical Impact |
|---------------|----------------------|----------------|
| Failed to fetch info data | The item’s pre-processing or retrieval script returned non-zero exit code or error output. | Immediate data loss for that poll. |
| No data for 30m | The item has not received any new value for the last 30 minutes (configured in zabbix_server.conf or item’s update interval). | Sustained monitoring outage. |
Zabbix’s ODBC DSN often uses Server=localhost\INSTANCE. This requires SQL Browser (UDP port 1434) to resolve the dynamic port. If SQL Browser is disabled, the connection hangs then fails.
Fix: Start SQL Browser and ensure Windows Firewall allows UDP 1434 inbound. When Zabbix fails to fetch MSSQL info data