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

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

Next, grant the necessary server-level roles and permissions:

If the Zabbix agent or server cannot physically reach the MSSQL port, data collection will halt completely.

Set the global plugin timeout using:

-- 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;

If you use a non-standard port or a named instance, ensure the correct port is defined. Use telnet or nc from the Zabbix server to test connectivity: zabbix mssql failed to fetch info data -or no data for 30m-

: Double-check credentials and ensure the SQL Server allows "SQL Server and Windows Authentication mode." 4. Agent 2 Specific Fixes If you are using Zabbix Agent 2 with the MSSQL plugin:

The most effective way to resolve this "no data" error is to use in your configuration. This bypasses common connection issues by explicitly defining the URI and credentials in the plugin configuration. Agent 2 Specific Fixes If you are using

On your MSSQL Host in the Zabbix UI, update the following Macros : $MSSQL.USER : zbx_monitor $MSSQL.PASSWORD :

Restart the Zabbix Agent 2 service.

To customize the time period or item, the standard expression for a 30-minute "no data" alert looks like this: nodata(/Host/mssql.info_item,30m)=1 If you'd like, I can help you:

The Zabbix server, proxy, or agent logs will provide the specific reason for the failure. To customize the time period or item, the