Zabbix Mssql Failed To Fetch Info Data -or No Data For 30m- -

When this trigger fires, the monitoring chain is broken at one of three levels: , Connectivity , or Configuration .

Problem: MSSQL: Failed to fetch info data (or no data for 30m)

"An answer," Tom said quietly. "The query is SELECT COUNT(*) FROM transactions WHERE timestamp > DATEADD(minute, -5, GETUTCDATE()) . It should return in milliseconds. But the execution plan shows a table scan on a table with 2.3 billion rows."

It outputs an explicit error message (e.g., "Login failed", "Connection refused") which points directly to the problem. Testing ODBC Connections:

ybcnyc. Junior Member. Joined: Jun 2022. Posts: 1. MSSQL monitoring - MSSQL: Failed to fetch info data (or no data for 30m) 16-06- zabbix mssql failed to fetch info data -or no data for 30m-

This alert triggers when the master item (often mssql.info.get or an ODBC data collector) fails to return valid JSON payload data to Zabbix. Because all dependent metrics rely on this payload, a failure here causes dozens of SQL items to break simultaneously.

: Verify the monitoring user has the required rights. For MSSQL 2022 , you must grant VIEW SERVER PERFORMANCE STATE and VIEW ANY DEFINITION . Trigger Expression Example

If this fails but isql succeeds, it strongly points to an issue with how the Zabbix server is invoking the ODBC subsystem. SELinux is a prime suspect here. Test by temporarily putting SELinux in permissive mode with setenforce 0 . If zabbix_get then works, you need to create SELinux policies to allow zabbix_server_t to connect to the SQL Server port.

Use modern FreeTDS 8.0 drivers, which are recommended for SQL Server 2016 and newer. 3. Root Cause: Network, Port, and Firewall Issues When this trigger fires, the monitoring chain is

Once the command-line test works, you can proceed to configure Zabbix.

Misconfigured or outdated ODBC drivers on the Zabbix server or proxy.

The following sections detail how to systematically investigate each of these areas.

: If using ODBC Driver 18, it defaults to encrypted connections. If you don't use SSL, add TrustServerCertificate=yes to your connection string or use Encrypt=no . 3. Validate ODBC Connectivity It should return in milliseconds

To test the connection directly from the Zabbix server command line, use the isql utility: isql -v YourDSNName your_zabbix_user your_password Use code with caution.

This specific error in typically triggers when the monitoring system hasn't received any data from the MSSQL instance for a prolonged period (30 minutes), often due to ODBC configuration issues or insufficient permissions for the monitoring user . Alert Message Draft

Navigate to > Hosts and click on your MSSQL host. Switch to the Macros tab. Verify the following inherited or host-level macros: $MSSQL.USER $MSSQL.PASSWORD