Zabbix Mssql Failed To Fetch Info Data -or No Data For 30m- < High-Quality >

: The monitoring user must have specific rights to view server state and access the . Use the following T-SQL to grant required permissions: GRANT VIEW SERVER STATE TO [zabbix_user] VIEW SERVER PERFORMANCE STATE for SQL 2022+) GRANT VIEW ANY DEFINITION TO [zabbix_user] Read access to msdb.dbo.sysjobs msdb.dbo.sysjobservers msdb.dbo.sysjobactivity Zabbix Git repository ODBC Configuration Issues (ODBC Template) Port Formatting

The customer portal, which relied on that data for a "system status" widget, showed a spinning circle. Then a dash. Then a blank page.

The "Failed to fetch info data" or "no data for 30m" error in Zabbix for MSSQL typically indicates a between your Zabbix server/proxy and the SQL instance . 🛠️ Quick Troubleshooting Checklist

Tom pulled up his own tools. "It's up. CPU 12%. Memory fine. Locks… no deadlocks. Connections…" He paused. "Huh. I see the Zabbix proxy connected. But it's just… waiting." zabbix mssql failed to fetch info data -or no data for 30m-

[MSSQL_DSN] ; This name will be used in the $MSSQL.DSN macro Driver = ODBC Driver 18 for SQL Server Server = 192.168.1.100 ; Your SQL Server IP or hostname Port = 1433 ; Usually the default port Database = master

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

If you continue to face issues after these steps, it is recommended to review the in the frontend to get specific error codes regarding the failed to fetch message. : The monitoring user must have specific rights

The monitoring user must have VIEW SERVER STATE (for SQL 2017/2019) or VIEW SERVER PERFORMANCE STATE (for SQL 2022).

If everything is configured correctly, you should see a Connected! message followed by an SQL> prompt. If you see an error, it's usually a configuration or driver issue. Additionally, test the connection using a simple query to ensure you can fetch data:

If the error logs suggest "Access Denied" or return null values for metrics. Then a blank page

: If your server uses a self-signed certificate, you may need to include TrustServerCertificate=Yes in your odbc.ini or connection string to prevent handshake failures.

Zabbix nodata trigger, really a lifesaver | by Werner Dijkerman

MSSQL: Failed to fetch info data (or no data for 30m) - suggestions * Posts. * Latest Activity. * Photos.

For Debian/Ubuntu systems, ensure the driver version supports your SQL Server. For example, msodbcsql18 is commonly used for modern versions. FreeTDS, while an open-source alternative, is sometimes the only option but can have TDS protocol version compatibility issues.