Two weeks ago, they had disabled the weekly index rebuild on the transactions table to speed up a different report. They had forgotten to re-enable it. The indexes had fragmented into digital gravel. A simple count query now took the server hostage.
On the other hand, the "No data for 30m" error usually indicates that Zabbix has not received any data from the MSSQL database for the past 30 minutes. This can be caused by:
nodata(/YourHost/perf_instance["SQLServer:Databases(_Total)\Data File(s) Size (KB)",_Total],30m)=1
Before touching configuration files, let’s decode what Zabbix is actually trying to tell you.
Two weeks ago, they had disabled the weekly index rebuild on the transactions table to speed up a different report. They had forgotten to re-enable it. The indexes had fragmented into digital gravel. A simple count query now took the server hostage.
On the other hand, the "No data for 30m" error usually indicates that Zabbix has not received any data from the MSSQL database for the past 30 minutes. This can be caused by: zabbix mssql failed to fetch info data -or no data for 30m-
nodata(/YourHost/perf_instance["SQLServer:Databases(_Total)\Data File(s) Size (KB)",_Total],30m)=1 Two weeks ago, they had disabled the weekly
Before touching configuration files, let’s decode what Zabbix is actually trying to tell you. Two weeks ago
