Your_Template:mssql.info.fetch.fail.min(30m)=1 or Your_Template:mssql.info.fetch.data.nodata(30m)=1
On the same SQL host, enable:
Trigger on nodata(5m) for a known always-increasing counter like system.uptime. If uptime stops reporting, your whole SQL monitoring is dead.
To confirm the fix, perform a manual query using zabbix_get from the Zabbix Server machine. This bypasses the frontend and allows immediate debugging.
Command:
zabbix_get -s <MSSQL_HOST_IP> -k "mssql.db.size[<DatabaseName>]"
(Invoking related search term suggestions)
The error "MSSQL: Failed to fetch info data (or no data for 30m)" typically indicates a communication failure between the Zabbix server/proxy and the Microsoft SQL instance, often stemming from ODBC misconfiguration, authentication issues, or network restrictions. Key Troubleshooting Areas
MSSQL: Failed to fetch info data (or no data for 30m) - Zabbix
tester777. Junior Member. Joined: Aug 2020. Posts: 9. #1. MSSQL: Failed to fetch info data (or no data for 30m) - suggestions. 18-
Problem: MSSQL: Failed to fetch info data (or no data for 30m)
PiotrJ. Junior Member. Joined: May 2023. Posts: 26. Problem: MSSQL: Failed to fetch info data (or no data for 30m) 21-09-2023, 19: zabbix mssql failed to fetch info data -or no data for 30m-
MSSQL: Failed to fetch info data (or no data for 30m) - Zabbix
ybcnyc. Junior Member. Joined: Jun 2022. Posts: 1. MSSQL monitoring - MSSQL: Failed to fetch info data (or no data for 30m) 16-06- ODBC Configuration & DSN
Port Formatting: MSSQL does not use the standard port= directive in odbc.ini. It must be specified with a comma after the IP address (e.g., Server = 192.168.1.100,1433).
Named Instances: If using a named instance, ensure the macro $MSSQL.INSTANCE is set correctly (e.g., MSSQL$InstanceName). For default instances, this macro should remain unchanged.
Trust Certificates: If you can connect via sqlcmd but not Zabbix, you may need to specify TrustServerCertificate=Yes in your odbc.ini file or ensure the Microsoft ODBC Driver 18 is properly handling encryption. Database Permissions
The Zabbix monitoring user needs specific permissions to gather performance data. Missing these will cause data fetching to fail even if the connection is established.
Required Permissions: GRANT VIEW SERVER STATE (or VIEW SERVER PERFORMANCE STATE for 2022+), VIEW ANY DEFINITION, and specific SELECT and EXECUTE rights on msdb objects. Zabbix Backend Configuration
ODBC Pollers: Ensure that ODBC pollers are active by setting StartODBCPollers to at least 1 in your zabbix_server.conf or zabbix_proxy.conf file.
Macro Settings: Verify that the host macros $MSSQL.USER, $MSSQL.PASSWORD, and $MSSQL.DSN exactly match the settings in your odbc.ini file. Network & Testing Your_Template:mssql
Connectivity Test: Run isql -v YourDSNName from the Zabbix server command line as the zabbix user to see if a raw ODBC connection works.
Agent 2 Plugins: If using Zabbix Agent 2, ensure the mssql.conf plugin file is present in the zabbix_agent2.d/plugins.d/ directory and that the Include= directive is active.
Are you using Zabbix Agent 2 or the ODBC-based template for this monitoring?
MSSQL: Failed to fetch info data (or no data for 30m) - Zabbix
tester777. Junior Member. Joined: Aug 2020. Posts: 9. #1. MSSQL: Failed to fetch info data (or no data for 30m) - suggestions. 18-
Problem: MSSQL: Failed to fetch info data (or no data for 30m)
PiotrJ. Junior Member. Joined: May 2023. Posts: 26. Problem: MSSQL: Failed to fetch info data (or no data for 30m) 21-09-2023, 19:
MSSQL: Failed to fetch info data (or no data for 30m) - Zabbix
ybcnyc. Junior Member. Joined: Jun 2022. Posts: 1. MSSQL monitoring - MSSQL: Failed to fetch info data (or no data for 30m) 16-06- Microsoft SQL monitoring and integration with Zabbix On the same SQL host, enable:
Troubleshooting Zabbix MSSQL: "Failed to fetch info data" or "No data for 30m" Errors
Zabbix is a popular monitoring tool used to track the performance and health of various systems, including Microsoft SQL Server (MSSQL) databases. However, users may sometimes encounter issues with Zabbix's MSSQL monitoring, such as "Failed to fetch info data" or "No data for 30m" errors. These errors can be frustrating and may indicate a problem with the database, the Zabbix agent, or the monitoring configuration. In this article, we'll explore the possible causes of these errors and provide step-by-step guides on how to troubleshoot and resolve them.
Understanding the Errors
The "Failed to fetch info data" error typically occurs when Zabbix's MSSQL monitoring item fails to retrieve data from the database. This can happen due to various reasons, such as:
On the other hand, the "No data for 30m" error usually indicates that Zabbix has not received any data from the MSSQL database for the past 30 minutes. This can be caused by:
Causes of the Errors
Before diving into the troubleshooting steps, it's essential to understand the possible causes of these errors. Some common causes include:
Troubleshooting Steps
To troubleshoot the "Failed to fetch info data" or "No data for 30m" errors, follow these steps: