Zabbix Mssql Failed To Fetch Info Data -or No Data For 30m- |best| 100%

This specific error in Zabbix 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

Preprocessing Issues: Check if the template's JSONPath preprocessing is failing due to spaces in counter names. For example, change Buffercachehitratio to Buffer cache hit ratio if the raw data includes spaces. zabbix mssql failed to fetch info data -or no data for 30m-

If manual fails, the issue is OS/ODBC layer. This specific error in Zabbix typically triggers when

file is often placed in a subdirectory that Agent 2 doesn't read by default . Move it to the zabbix_agent2.d directory or ensure your zabbix_agent2.conf includes a path to it (e.g., Include=./zabbix_agent2.d/plugins.d/*.conf Restart Required From Zabbix server/proxy host (example using sqlcmd): sqlcmd

Trust Certificate: If using ODBC Driver 18, you may need to add TrustServerCertificate=yes to your connection string in /etc/odbc.ini to handle self-signed SSL.

Part 1: Understanding the Error Messages

Before touching configuration files, let’s decode what Zabbix is actually trying to tell you.

Minimal diagnostic commands/examples

• From Zabbix server/proxy host (example using sqlcmd):

  sqlcmd -S sqlserver.example.com -U monitoring_user -P 'password' -Q "SELECT 1"
  

• Check ODBC (unixODBC):

  isql -v MSSQL_DSN monitoring_user password
  

• Tail Zabbix logs:

  tail -n 200 /var/log/zabbix/zabbix_server.log | grep -i mssql
  tail -f /var/log/zabbix/zabbix_server.log
  

The Silent Screen