ZBX MSSQL Monitor

Purpose and user intent: The ZBX MSSQL Monitor provides integration between Microsoft SQL Server metrics and the Zabbix monitoring platform. It targets DBAs, SREs, DevOps and IT operations teams that need centralized visibility, proactive health checks, and scalable alerting for SQL Server deployments. Core logic and features: It collects CPU, memory, I/O, and wait statistics from SQL Server DMVs, tracks blocking and deadlocks, and measures query latency. It auto-discovers databases and instances, normalizes metrics, and ships them into Zabbix templates for consistent dashboards. Optional advanced metrics include SLA trend analysis, anomaly detection, and cross-instance correlation. The solution is designed to be lightweight, with read-only access and support for multiple authentication modes, enabling safe deployment in production. Inputs & outputs: Inputs include host, port, authentication method, credentials (when required), instance name, and collection interval. Outputs include structured metric fields such as cpu_usage_percent, memory_usage_percent, io_latency_ms, wait_time_ms, blocking_rate, deadlock_count, and avg_query_latency_ms, exposed to Zabbix as items. Algorithms & calculations: Metrics are derived from SQL Server DMVs and system views. Averages, percent utilization, and percentiles are computed over the collection window. Baselines and simple anomaly scoring can be configured; SLA calculations use historical uptime and sample durations. Error & edge cases: Handles connectivity failures, insufficient privileges, credential changes, and database name changes. If a database is offline, metrics for that database are skipped but others remain active. Insufficient privileges yield partial metrics with diagnostic logs. Network outages propagate to the monitoring channel and may trigger alerts. Industry/Region & Localization: Uses UTC timestamps and standard SQL Server metrics. Supports SQL Server on Windows and Linux; units follow SQL Server conventions. Assumptions & Exclusions: Assumes read-only access to DMVs and appropriate permissions. Not a full query-tuning tool; no server-side changes are performed. Excludes non-SQL Server platforms.