Our SQL Server check is currently limited to collecting metrics from the sys.dm_os_performance_counters table, and by default it only collects what metrics we think are the most likely to be relevant. True, with some simple configuration, you can extend what metrics are collected from that table, but there may be cases where you're interested in collecting more than what is available in that table at all.
In these cases, you might consider our WMI check as an additional source of SQL Server metrics (and if you're not familiar with the WMI check yet, you can find a great guide for implementing that here). Some WMI classes may be available that can contain additional performance data about your SQL Server (such as Win32_PerfFormattedData_SQLSERVERAGENT_SQLAgentJobs), and you may be able to use our WMI check to query them for additional metric collection.
For example, we've had some users employ our WMI check with the following configuration to collect a gauge metric for the number of failed jobs in their SQL Server:
- class: Win32_PerfRawData_SQLSERVERAGENT_SQLAgentJobs
- [Failedjobs, sqlserver.failed_jobs, gauge]
- Name: _Total