Here is an example configuration for monitoring an MSSQL database in Zabbix:
The SQL Server must be reachable over TCP port 1433 (or your custom port) from the Zabbix server/proxy or agent. Step-by-Step Troubleshooting Guide 1. Verify MSSQL Permissions zabbix mssql failed to fetch info data -or no data for 30m-
The cause of this "no data" scenario is almost never a single, obvious problem. It is typically the result of a breakdown somewhere in the complex chain of connections that spans from the Zabbix server all the way to the SQL Server's internal performance counters. This guide provides a systematic, step-by-step approach to diagnose and resolve the issue. Here is an example configuration for monitoring an
to identify network-related or instance-specific connection failures Troubleshooting Steps zabbix mssql failed to fetch info data -or no data for 30m-
: In mssql.conf , define your connection sessions clearly: Plugins.MSSQL.Sessions. .Uri=sqlserver:// :1433 .
Micah's Edge © 2026