Nagios Support Forum

Good morning,

I'm new here and I would like to apologize in advance if this is not the correct forum to post in. I have a question and an issue, both related to the default MSSQL checks in Nagios(XI).

Our MSSQL Log Truncations check reports that the Log Truncations is currently at 180.0. I've tried to find information about Truncations but I cannot find any good value for warning/critical levels for a (most of the time) busy SQL server. Can anyone help me in the right direction here, perhaps with some documentations?


Then the issue that we have. I've added checks for multiple databases through Configure -> Run the monitoring wizard -> MSSQL Database. In those databases I've created a new login named Nagios with a default password that we have for these kind of things. While going through the monitoring wizard I've entered the name/password correctly in all checks, but on one database it fails with this error:

<class 'pymssql.InterfaceError'>
Caught unexpected error. This could be caused by your sysperfinfo not containing the proper entries for this query, and you may delete this service check.

SQL Server version: SQL Server 2008 R2
- SQL Server Management Studio: 10.50.2500.0
- Data Access Components (MDAC): 6.1.7601.17514
- MSXML: 3.0.4.0.6.0 (Note: On the working server this version is 3.0.5.0.6.0)
- Internet Explorer: 9.11.9600.17041
- .Net Framework: 2.0.50727.5477
- Operating system: Windows Server 2008 R2 Standard: 6.1.7601

Any assistance provided would be greatly appreciated! If any more information is required I'd be happy to provide it.

Kind regards,
Dennis

I honestly couldn't answer your first question regarding warning and critical thresholds for truncations. However on your second one, if you are not checking the master db, your db will not likely have the sysperfinfo table and so that check will fail. This is somewhat expected, although not really mentioned. So with that, are you checking the master db or a separate one?

Hello sreinhardt,

We're not checking the masterdb. I've looked at the location where the sysperfinfo should be located and it is indeed missing (should have checked that earlier ^_^). I'll take a look at any possible installation guides and time the installation outside the production hours. Thanks.

Excellent, sounds like a job for your MSSQL DBA. Give us a shout if it's still not checking properly.