-- For SQL Server 2022 and newer CREATE LOGIN zabbix WITH PASSWORD = 'YourSecurePassword'; GRANT VIEW SERVER PERFORMANCE STATE TO zabbix; GRANT VIEW ANY DEFINITION TO zabbix; GO -- For SQL Server 2017 and 2019 -- USE THE FOLLOWING INSTEAD: -- GRANT VIEW SERVER STATE TO zabbix; Use code with caution. Step 2: Grant MSDB Agent Access
Create a custom UserParameter that uses the localized name, or switch to the sql.count item using T-SQL queries instead of perfmon.
The Zabbix Agent runs as SYSTEM (or a local user), but SQL Server restricts access to Dynamic Management Views (DMVs) like sys.dm_os_performance_counters . zabbix mssql failed to fetch info data -or no data for 30m-
When Zabbix says "failed to fetch info data," it means the agent attempted to execute a query (likely against performance counters or DMVs) and received:
This is a generic trigger often seen when using the "MSSQL by ODBC" or "MSSQL by Zabbix agent 2" templates. It indicates that the master "Info" item—which discovery and other dependent items rely on—is not receiving data. Core Causes & Fixes 1. Database Permissions (Most Common) -- For SQL Server 2022 and newer CREATE
If isql fails, your Linux machine cannot talk to SQL Server. Check your network firewalls and verify /etc/odbc.ini .
If any returns empty, debug before production. When Zabbix says "failed to fetch info data,"
. This usually occurs when using the "MSSQL by ODBC" or "MSSQL by Zabbix agent 2" templates. Common Solutions Trust Server Certificate (ODBC Driver 18+)
The most frequent cause of this error is a change in the monitoring user's password or an incorrectly typed macro in Zabbix. Open your Zabbix Frontend.