To resolve this issue efficiently, it helps to understand why the master item stops retrieving data. The problem typically falls into one of four categories:
On your Zabbix server or proxy, install the necessary packages:
nodata(/YourHost/perf_instance["SQLServer:Databases(_Total)\Data File(s) Size (KB)",_Total],30m)=1 and last(/YourHost/perf_instance[...])<>0 zabbix mssql failed to fetch info data -or no data for 30m-
: Ensure the odbc.ini file does not store credentials. For Zabbix, username and password should be passed as arguments from the frontend.
The Network Operations Center hummed its usual lullaby of cooling fans and low conversation. On the wall, a massive screen displayed a constellation of green dots—each one a server, a service, a heartbeat. In the center of that constellation, glowing a steady, reassuring emerald, was . To resolve this issue efficiently, it helps to
. If your server isn't configured for it, connection attempts will fail Check for driver-specific errors in the Zabbix Server or Proxy logs
-- Grant permissions in the msdb database USE msdb; CREATE USER zbx_monitor FOR LOGIN zbx_monitor; GRANT EXECUTE ON msdb.dbo.agent_datetime TO zbx_monitor; GRANT SELECT ON msdb.dbo.sysjobactivity TO zbx_monitor; GRANT SELECT ON msdb.dbo.sysjobservers TO zbx_monitor; GRANT SELECT ON msdb.dbo.sysjobs TO zbx_monitor; The Network Operations Center hummed its usual lullaby
Sometimes, SQL Server performance counters become corrupted or disabled. If Zabbix relies on WMI or performance counters directly, this will result in "no data."
Which and MSSQL template are you currently using? Is your Zabbix server running on Linux or Windows ?