When this trigger fires, the monitoring chain is broken at one of three levels: , Connectivity , or Configuration .
When using Zabbix Agent 2, the mssql.conf plugin file must be present in the plugins.d directory, and the agent must be restarted to load it.
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
Ensure your Zabbix monitoring user (e.g., zbx_monitor ) has the necessary permissions. Run these T-SQL commands on the target SQL Server: Zabbixhttps://www.zabbix.com Microsoft SQL monitoring and integration with Zabbix
The monitoring user must have specific rights to query system views like sys.dm_os_performance_counters . Without VIEW SERVER STATE (or VIEW SERVER PERFORMANCE STATE for SQL 2022+), the "Get Info" queries return empty results.
When this trigger fires, the monitoring chain is broken at one of three levels: , Connectivity , or Configuration .
When using Zabbix Agent 2, the mssql.conf plugin file must be present in the plugins.d directory, and the agent must be restarted to load it. zabbix mssql failed to fetch info data -or no data for 30m-
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 When this trigger fires, the monitoring chain is
Ensure your Zabbix monitoring user (e.g., zbx_monitor ) has the necessary permissions. Run these T-SQL commands on the target SQL Server: Zabbixhttps://www.zabbix.com Microsoft SQL monitoring and integration with Zabbix Step-by-Step Troubleshooting Guide 1
The monitoring user must have specific rights to query system views like sys.dm_os_performance_counters . Without VIEW SERVER STATE (or VIEW SERVER PERFORMANCE STATE for SQL 2022+), the "Get Info" queries return empty results.