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

If using , verify that the mssql.conf plugin file is correctly configured and included in the main agent configuration. Check for these specific macros in the Zabbix frontend:

The “failed to fetch info data (or no data for 30m)” error in MSSQL environments is rarely a single‑point failure but often a symptom of network, performance, or resource bottlenecks. A systematic diagnostic approach—starting with blocking analysis and connectivity tests—can quickly resolve the issue. Long‑term, moving to incremental data collection and asynchronous monitoring eliminates the risk of 30‑minute blackouts. mssql: failed to fetch info data (or no data for 30m)

If the SQL Server looks healthy, the issue may be with the monitoring agent itself. If using , verify that the mssql

Thanks for the question and using MS Q&A platform. * I have encountered a similar issue and found that the error "Failed to fetch" Microsoft Learn Resolving no data error for MSSQL performance metrics If you encounter 'The user does not have permission to perform this action' message while running the query, then update the permi... PitStop ManageEngine Troubleshooting DBM Setup for SQL Server - Datadog Docs Check the TCP connection from the agent to the host by running telnet host port to make sure there is network connectivity fro... Datadog Docs MSSQL: Failed to fetch info data (or no data for 30m) - ZABBIX Forums Jun 16, 2022 — * I have encountered a similar issue and

If this is a one-time event, it was likely a temporary network glitch or a momentary resource spike. If it is persistent, it is likely a firewall block or a permission issue with the monitoring user.