MSSQL Database Monitor not working 2008R2
Posted: Thu Sep 05, 2013 1:20 pm
Hi,
MSSQL Server monitor works fine, but the DB monitor has multiple issues. I am testing on MSSQL 2008 R2 from Nagios XI 2012R2.3. I believe that I am running the latest version of the plugin:
Here is the result:
MSSQL Active Transactions
Unknown 8m 40s 5/5 2013-09-05 14:06:33 SQL Server message 208, severity 16, state 1, line 1:
MSSQL Connection Time
Ok 6m 58s 1/5 2013-09-05 14:09:15 OK: Time to connect was 0.00593996047974s
MSSQL Log Cache Hit Rate
Unknown 10m 19s 5/5 2013-09-05 14:09:54 SQL Server message 208, severity 16, state 1, line 1:
MSSQL Log File Usage
Unknown 8m 37s 5/5 2013-09-05 14:06:36 SQL Server message 208, severity 16, state 1, line 1:
MSSQL Log Flush Wait Time
Unknown 6m 54s 5/5 2013-09-05 14:08:19 SQL Server message 208, severity 16, state 1, line 1:
MSSQL Log Growths
Unknown 10m 15s 5/5 2013-09-05 14:09:58 SQL Server message 208, severity 16, state 1, line 1:
MSSQL Log Shrinks
Unknown 8m 33s 5/5 2013-09-05 14:06:40 SQL Server message 208, severity 16, state 1, line 1:
MSSQL Log Truncations
Unknown 6m 50s 5/5 2013-09-05 14:08:23 SQL Server message 208, severity 16, state 1, line 1:
MSSQL Transactions / Sec
Critical 10m 12s 5/5 2013-09-05 14:10:01 (null)
For the unknown status, it seems that Nagios is looking for the sys.sysperInfo table which has been depricated in 08 which uses sys.dm_os_performance _counters.
The MSSQL Transactions / Sec returns the following:
[root@nagios libexec]# ./check_mssql_database.py -H ********* -U 'sa' -P '**********' -T 'db_name' -p 1433 --transpsec --warning 10 --critical 20
Usage: check_mssql_database.py -H hostname -U user -P password -T table --mode
check_mssql_database.py: error: no such option: --transpsec
Any help much appreciated.
MSSQL Server monitor works fine, but the DB monitor has multiple issues. I am testing on MSSQL 2008 R2 from Nagios XI 2012R2.3. I believe that I am running the latest version of the plugin:
Here is the result:
MSSQL Active Transactions
Unknown 8m 40s 5/5 2013-09-05 14:06:33 SQL Server message 208, severity 16, state 1, line 1:
MSSQL Connection Time
Ok 6m 58s 1/5 2013-09-05 14:09:15 OK: Time to connect was 0.00593996047974s
MSSQL Log Cache Hit Rate
Unknown 10m 19s 5/5 2013-09-05 14:09:54 SQL Server message 208, severity 16, state 1, line 1:
MSSQL Log File Usage
Unknown 8m 37s 5/5 2013-09-05 14:06:36 SQL Server message 208, severity 16, state 1, line 1:
MSSQL Log Flush Wait Time
Unknown 6m 54s 5/5 2013-09-05 14:08:19 SQL Server message 208, severity 16, state 1, line 1:
MSSQL Log Growths
Unknown 10m 15s 5/5 2013-09-05 14:09:58 SQL Server message 208, severity 16, state 1, line 1:
MSSQL Log Shrinks
Unknown 8m 33s 5/5 2013-09-05 14:06:40 SQL Server message 208, severity 16, state 1, line 1:
MSSQL Log Truncations
Unknown 6m 50s 5/5 2013-09-05 14:08:23 SQL Server message 208, severity 16, state 1, line 1:
MSSQL Transactions / Sec
Critical 10m 12s 5/5 2013-09-05 14:10:01 (null)
For the unknown status, it seems that Nagios is looking for the sys.sysperInfo table which has been depricated in 08 which uses sys.dm_os_performance _counters.
The MSSQL Transactions / Sec returns the following:
[root@nagios libexec]# ./check_mssql_database.py -H ********* -U 'sa' -P '**********' -T 'db_name' -p 1433 --transpsec --warning 10 --critical 20
Usage: check_mssql_database.py -H hostname -U user -P password -T table --mode
check_mssql_database.py: error: no such option: --transpsec
Any help much appreciated.