Wizard MSSQL Database (monitoring LogFileUsage)

[detronict]

Thanks abrist, but i know that.
My user is serveradmin and has datareader rights on all databases.

Removing the -T from the command gives an obvious error that the command is invalid. (database name without -T
Removing both -T and the databasename gives error: "check_mssql_database.py: error: Table is a required option."

I also know that only the master table database contains the sysperfinfo elements,
But according to scottwilkerson:

This is correct, however the sysperfinfo table in master contains the logfiles sized of the databases you are looking at

He does not tell me however how to use the wizard in a way that it will work.

It looks as if everyone has an opinion, but no one has an answer!

I have 3 very simple questios:

1. Are all the elements in the wizard "MSSQL Database" valid for all tables?
2. Is there anybody who has this operational?
3. Does anyone have a halfway decent manual about using NagioXI to monitor MSSQL databases!!!

If I sound bitchy i appologyze, but i am getting frustrated by the whole world saying it should work and nobody able to tell me how to do it.
If the wizard is not functional for all databases i'd rather now that than wasting huge amounts of time trying to get it to do what it cannot do!

I still appreciate all the help i can get guys!!

[lmiltchev]

1. Are all the elements in the wizard "MSSQL Database" valid for all tables?

They should be as far as I know.

2. Is there anybody who has this operational?

I ran the check against a few different databases and didn't get any errors. What is the Nagios XI version that you are currently using? What is the version of the "MSSQL Database" wizard that you are using? (Admin->Manage Config Wizards)
Is this the only check you are having issues with?

3. Does anyone have a halfway decent manual about using NagioXI to monitor MSSQL databases!!!

There hasn't been a need for a document, since running the wizard is pretty much straight forward process. I believe the only document we have is this one:
http://assets.nagios.com/downloads/nagi ... rereqs.pdf
It may be useful to people running older version of Nagios XI.
Note: You can always view the plugin's usage by running in terminal:

Code: Select all

/usr/local/nagios/libexec/check_mssql_database.py -h

[detronict]

The wizard version is 1.51 and is shown as "up to date".

I have done this command

/usr/local/nagios/libexec/check_mssql_database.py -H 172.16.1.51 -U 'sa' -P 'XXXXXXX' -T 'master' -I NI01 --test

With this result

logshrinks passed!
logfileusage passed!
logwait passed!
transpec failed with: 'MSSQLDeltaQuery' object has no attribute 'table'
datasize passed!
activetrans passed!
logflushes failed with: 'MSSQLDeltaQuery' object has no attribute 'table'
logcachehit passed!
loggrowths passed!
logtruncs passed!
2/10 tests failed.

The same command on another database:

[root@arlnij-rhn01 ~]# /usr/local/nagios/libexec/check_mssql_database.py -H 172.16.1.51 -U 'sa' -P 'XXXXXXX' -T 'consulinkv4' -I NI01 --test
logshrinks failed with: SQL Server message 208, severity 16, state 1, line 1:
Invalid object name 'sysperfinfo'.
DB-Lib error message 208, severity 16:
General SQL Server error: Check messages from the SQL Server

logfileusage failed with: SQL Server message 208, severity 16, state 1, line 1:
Invalid object name 'sysperfinfo'.
DB-Lib error message 208, severity 16:
General SQL Server error: Check messages from the SQL Server

logwait failed with: SQL Server message 208, severity 16, state 1, line 1:
Invalid object name 'sysperfinfo'.
DB-Lib error message 208, severity 16:
General SQL Server error: Check messages from the SQL Server

transpec failed with: SQL Server message 208, severity 16, state 1, line 1:
Invalid object name 'sysperfinfo'.
DB-Lib error message 208, severity 16:
General SQL Server error: Check messages from the SQL Server

datasize failed with: SQL Server message 208, severity 16, state 1, line 1:
Invalid object name 'sysperfinfo'.
DB-Lib error message 208, severity 16:
General SQL Server error: Check messages from the SQL Server

activetrans failed with: SQL Server message 208, severity 16, state 1, line 1:
Invalid object name 'sysperfinfo'.
DB-Lib error message 208, severity 16:
General SQL Server error: Check messages from the SQL Server

logflushes failed with: SQL Server message 208, severity 16, state 1, line 1:
Invalid object name 'sysperfinfo'.
DB-Lib error message 208, severity 16:
General SQL Server error: Check messages from the SQL Server

logcachehit failed with: SQL Server message 208, severity 16, state 1, line 1:
Invalid object name 'sysperfinfo'.
DB-Lib error message 208, severity 16:
General SQL Server error: Check messages from the SQL Server

loggrowths failed with: SQL Server message 208, severity 16, state 1, line 1:
Invalid object name 'sysperfinfo'.
DB-Lib error message 208, severity 16:
General SQL Server error: Check messages from the SQL Server

logtruncs failed with: SQL Server message 208, severity 16, state 1, line 1:
Invalid object name 'sysperfinfo'.
DB-Lib error message 208, severity 16:
General SQL Server error: Check messages from the SQL Server

10/10 tests failed.

It works on the master database but not on any other. I have used the sa user so access rights shouldn't be the issue.

The only thing working on all databases is --time2connect option.

Can you show me an example (and the result) of the --test option on a database other than master?

Another thing i stumbled accross an issue from October 2013.(http://support.nagios.com/forum/viewtop ... 16&t=21791)
This describes a bug in the plugin that causes the --datasize option to do the same thing as the loggrowths option.

The bug is still there. I think this is strange because the solution is in that thread also. (I have tested it and it works)
Since the wizard is installed as a supported element along with NagiosXI I would expect that this problem had been resolved, or at least a warning about this behaviour.
Are the supported plugins checked before they are bundled with NagiosXI?

[abrist]

I have opened an internal bug report for this issue. My apologies, we will get to the bottom of it.