Zabbix Mssql Failed To Fetch Info Data -or No Data For 30m- ((full))

Here is an example configuration for monitoring an MSSQL database in Zabbix:

21 Sept 2023 — PiotrJ. Junior Member. Joined: May 2023. Posts: 26. Problem: MSSQL: Failed to fetch info data (or no data for 30m) 21-09-2023, 19:

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

Leila, the senior on-call engineer, nursed her third coffee of the morning. She glanced at the dashboard. All green. A quiet Tuesday. zabbix mssql failed to fetch info data -or no data for 30m-

Even if a connection is established, the provided user may lack the necessary permissions to query the required system tables and performance counters. A key symptom here is that some items, such as uptime or version information, might work, while others that require deeper system access (like performance counters) fail. This partial success is a strong clue pointing to a permissions issue.

From your Zabbix server, run: telnet

If you are using the , the connection goes through unixODBC and a database driver installed on your Zabbix server or proxy. 1. Correct the Connection String Syntax Here is an example configuration for monitoring an

systemctl status zabbix-agent

Problem: MSSQL: Failed to fetch info data (or no data for 30m)

: Zabbix needs to read from the msdb database for job status:%%MAGIT_PARSER_PROTECT%% sql USE msdb; GRANT SELECT ON dbo.sysjobs TO zabbix; GRANT SELECT ON dbo.sysjobservers TO zabbix; GRANT SELECT ON dbo.sysjobactivity TO zabbix; GRANT EXECUTE ON dbo.agent_datetime TO zabbix; %%MAGIT_PARSER_PROTECT%% 3. Agent 2 Plugin Configuration Posts: 26

By following this structural troubleshooting pathway, you can quickly pinpoint why Zabbix is failing to fetch MSSQL data and clear the 30-minute dead-stop alert. To help narrow this down further, let me know: Are you using or an ODBC template ?

: Set DebugLevel=4 in your Zabbix Agent or Server configuration and restart. Check the logs for specific ODBC error codes (e.g., [08001] for network issues).