zabbix_get -s <SQL_HOST_IP> -k "agent.ping"
Apply these in zabbix_agentd.conf :
Example:
Problem: MSSQL: Failed to fetch info data (or no data for 30m)
: Verify the monitoring user has the required rights. For MSSQL 2022 , you must grant VIEW SERVER PERFORMANCE STATE and VIEW ANY DEFINITION . Trigger Expression Example zabbix mssql failed to fetch info data -or no data for 30m-
Problem: MSSQL: Failed to fetch info data (or no data for 30m)
CREATE LOGIN zabbix_svc WITH PASSWORD = 'StrongPwd!'; CREATE USER zabbix_svc FOR LOGIN zabbix_svc; GRANT VIEW SERVER STATE TO zabbix_svc; GRANT VIEW ANY DATABASE TO zabbix_svc; GRANT CONNECT SQL TO zabbix_svc; zabbix_get -s <SQL_HOST_IP> -k "agent
"action_name": "MSSQL Fetch Failure Alert", "conditions": "trigger_name": "MSSQL: Failed to fetch info data OR no data for 30m", "trigger_severity": ["high", "disaster"] , "operations": "default_subject": "CRITICAL: MSSQL data fetch failed on HOST.NAME", "default_message": "Problem started at EVENT.TIME on EVENT.DATE\n Problem name: TRIGGER.NAME\n Host: HOST.NAME\n Severity: TRIGGER.SEVERITY\n\n Original event ID: EVENT.ID\n Check MSSQL connectivity:\n 1. Verify SQL Server is running\n 2. Check firewall rules\n 3. Validate credentials in Zabbix configuration\n 4. Review SQL error logs\n\n Last 5 fetch attempts: ITEM.VALUE<ms.sql[fetch_data],5>", "recovery_subject": "RECOVERY: MSSQL fetch restored on HOST.NAME", "recovery_message": "Problem resolved at EVENT.RECOVERY.TIME\n Duration: EVENT.DURATION\n Host: HOST.NAME"