nc -zv <SQL_Server_IP> <PORT>
# Syntax: isql -v isql -v MSSQL_DSN zabbix_user my_password Use code with caution. Copied to clipboard
Change to:
The "failed to fetch info data (or no data for 30m)" error in Zabbix is not a single, specific problem but a generic alert that indicates a breakdown in the data collection chain. When you link the "MSSQL by ODBC" template to a host, Zabbix starts executing a series of discovery rules and item checks. This specific error usually appears when a master item for data discovery fails to return any data, which in turn prevents all dependent items from collecting metrics. Essentially, the initial data-gathering step has failed, leaving the rest of the dashboard empty.
user wants a long, detailed article about the Zabbix error "failed to fetch info data -or no data for 30m-" for MS SQL Server monitoring. I need to provide a comprehensive guide covering causes, diagnostics, and solutions. To do this, I need to gather information from various sources. I'll start with a broad search to get an overview of the issue and then follow up with more specific searches to cover different aspects. search results show some potentially useful links. I need to gather more specific information. I'll open the results that seem most relevant to the error message and the troubleshooting process. have gathered information from various sources. The search results cover the error message, troubleshooting steps, configuration best practices, ODBC setup, and known issues. I will now structure a comprehensive article that covers the following key sections: an introduction and context, common causes and error messages, prerequisites, macro configuration, ODBC driver setup, testing connectivity, instance name issues, troubleshooting, advanced topics, and a conclusion and recommendations. I will use the gathered information to support each section. error message is one of the most common and frustrating hurdles when setting up database monitoring in Zabbix, but it's also a signal that can guide you directly to the root cause. This article will decode what the message means and provide a complete, step-by-step guide to diagnosing and fixing the issue for good. zabbix mssql failed to fetch info data -or no data for 30m-
or Zabbix macros, the port must be specified after a comma, not a colon (e.g., Server = 192.168.1.50,1433 as a separate directive often fails. Macro Configuration : Verify that your host macros are correctly set: $MSSQL.USER $MSSQL.PASSWORD $MSSQL.DSN (must match the name in your /etc/odbc.ini on the Zabbix server/proxy). Agent 2 Configuration
Apply these in zabbix_agentd.conf :
Look for entries containing mssql or odbc . Common errors include:
The error 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 nc -zv <SQL_Server_IP> <PORT> # Syntax: isql -v
nodata(/YourHost/perf_instance["SQLServer:Databases(_Total)\Data File(s) Size (KB)",_Total],30m)=1 and last(/YourHost/perf_instance[...])<>0
systemctl status zabbix-agent
Simple connectivity problems can cause this error. The server may be unreachable due to network problems, the configured TCP port may be incorrect or blocked by a firewall, or the dynamic port configuration could be causing intermittent failures.
From the Zabbix server CLI:
tester777. Junior Member. Joined: Aug 2020. Posts: 9. #1. MSSQL: Failed to fetch info data (or no data for 30m) - suggestions. 18-
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:
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.
ybcnyc. Junior Member. Joined: Jun 2022. Posts: 1. MSSQL monitoring - MSSQL: Failed to fetch info data (or no data for 30m) 16-06- This specific error usually appears when a master