-or No Data For 30m- Better: Zabbix Mssql Failed To Fetch Info Data

Introduction

Zabbix is a popular monitoring tool used to track the performance and health of various systems, including Microsoft SQL Server (MSSQL) databases. However, sometimes Zabbix may encounter issues while monitoring MSSQL databases, resulting in errors such as "failed to fetch info data" or "no data for 30m". This guide aims to provide a step-by-step approach to troubleshooting these issues.

Possible Causes

Before diving into the troubleshooting steps, it's essential to understand the possible causes of these errors: zabbix mssql failed to fetch info data -or no data for 30m-

1. Incorrect configuration: Incorrect or incomplete configuration of the Zabbix MSSQL monitoring setup.
2. Connectivity issues: Issues with the network connectivity between the Zabbix server and the MSSQL database.
3. MSSQL configuration: Incorrect configuration of the MSSQL database, such as disabled SQL Server Agent or incorrect permissions.
4. Zabbix agent issues: Issues with the Zabbix agent running on the MSSQL server.

Troubleshooting Steps

White Paper: Troubleshooting "No Data" for MSSQL Monitoring in Zabbix

Subject: Resolving "Failed to fetch info data" and "No data for 30m" errors for Microsoft SQL Server. Audience: System Administrators, DevOps Engineers, DBAs.

Minimal diagnostic commands/examples

• From Zabbix server/proxy host (example using sqlcmd):

  sqlcmd -S sqlserver.example.com -U monitoring_user -P 'password' -Q "SELECT 1"
  

• Check ODBC (unixODBC):

  isql -v MSSQL_DSN monitoring_user password
  

• Tail Zabbix logs:

  tail -n 200 /var/log/zabbix/zabbix_server.log | grep -i mssql
  tail -f /var/log/zabbix/zabbix_server.log
  

Step 6: Performance Counter Corruption

Sometimes, SQL Server performance counters become corrupted or disabled. If Zabbix relies on WMI or performance counters directly, this will result in "no data." Introduction Zabbix is a popular monitoring tool used

Rebuild Counters (Run in CMD as Admin):

1. Unload the counters: unlodctr mssqlserver
2. Reload the counters (navigate to the SQL Binn folder first, usually C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Binn): lodctr perf-MSSQLSERVERsqlctr.ini
3. Restart the SQL Server service.

Step 4: Analyze Monitoring Item Configuration

1. Review the monitoring item configuration in Zabbix and ensure that it's set up correctly.
2. Verify that the query syntax is correct and the database connection is properly configured.
3. Check the monitoring item's history and trends to see if there are any issues with data collection.

Step 5: Test MSSQL Connection

1. Test connection: Use a tool like mssql-cli or sqlcmd to test the connection to the MSSQL database using the Zabbix monitoring account.

Example:

mssql-cli -S <MSSQL_server_IP> -U <Zabbix_monitoring_account> -P <password>

If the connection is successful, you should see a prompt. If the connection is successful

Step 2: Verify Zabbix Agent Connectivity

If the SQL service is running, the issue might be between the Zabbix Server and the Agent on the SQL host.

On the Zabbix Server, run:

zabbix_get -s <TARGET_IP> -k agent.ping

• If you get a response: The agent is up, but the MSSQL plugin is failing.
• If you get no response: Check firewalls (port 10050) or verify the agent service is running on the host.