Zabbix Mssql Failed To Fetch Info Data -or No Data For 30m- 【2K 2024】
USE msdb; CREATE USER zbx_monitor FOR LOGIN zbx_monitor; GRANT SELECT ON msdb.dbo.sysjobs TO zbx_monitor; GRANT SELECT ON msdb.dbo.sysjobservers TO zbx_monitor; GRANT SELECT ON msdb.dbo.sysjobactivity TO zbx_monitor; GRANT EXECUTE ON msdb.dbo.agent_datetime TO zbx_monitor;
Format the server and port separated strictly by a comma: Server = 192.168.1.50,1433 Use code with caution. 2. Handle Encryption and Self-Signed Certificates zabbix mssql failed to fetch info data -or no data for 30m-
Troubleshooting Zabbix: MSSQL Failed to Fetch Info Data / No Data for 30m USE msdb; CREATE USER zbx_monitor FOR LOGIN zbx_monitor;
Zabbix is a popular monitoring tool used to track the performance and health of various systems, including Microsoft SQL Server (MSSQL) databases. However, users may sometimes encounter issues with Zabbix's MSSQL monitoring, such as "Failed to fetch info data" or "No data for 30m" errors. These errors can be frustrating and may indicate a problem with the database, the Zabbix agent, or the monitoring configuration. In this article, we'll explore the possible causes of these errors and provide step-by-step guides on how to troubleshoot and resolve them. However, users may sometimes encounter issues with Zabbix's
If isql works, your macros are correct, and the user has the right permissions, but you still get "no data," the issue is often more subtle and lies in how the template's preprocessing rules interact with your specific SQL Server instance.
The user must have VIEW SERVER STATE and VIEW ANY DEFINITION permissions on the MSSQL instance. C. Check Network and Firewall The default MSSQL port is TCP 1433. Telnet/NC Test: From the Zabbix Proxy/Server, run: nc -zv 1433 Use code with caution.
file on the target host. Restart the Zabbix Agent 2 service after making any changes. Macro URI Errors : Ensure the $MSSQL.URI macro is correctly formatted as sqlserver:// : or uses a named session defined in the agent configuration. Troubleshooting Steps Test Connection Manually (for ODBC) or