NAGIOS XI Oracle and SQL Monitoring

[desmondlewissmith]

Probably a newb question, but wondering if there are plugins available for somewhat granualar monitoring of Oracle and SQL Servers other than power and ping in NAGIOS XI.

[nscott]

Desmond,

There are plugins on the exchange that could help you with both, however at this time there are no official wizards for either. But there are many plugins for you to use, its just not in a wrapped-up-in-a-bow format like a wizard:

http://exchange.nagios.org/index.php?op ... ord=oracle

HOWEVER, at this very moment I am working on a MSSQL wizard, is that the SQL you were talking about? If it was, then I would greatly appreciate a beta tester, as I'm working in a fairly controlled environment.

[desmondlewissmith]

I would love to beta test your SQL pluggin. I'm running a lot of MS SQL Servers and can test on my DEV infrastructure.

[nscott]

Desmond,

Thats great! I will post them here then! There are three wizards, and I'm more used to a MySQL so I would like to hear from a MSSQL admin how things should be done with these wizards. If you've never installed a wizard in Nagios XI here is a howto for that:

http://assets.nagios.com/downloads/nagi ... izards.pdf

Also, one last thing you'll need to install on your nagios xi server is:

Code: Select all

yum intall pymssql -y

Other than that you should just be able to install these wizards and go. Just so you know whats going in in these plugins, they aren't going to tax your database very much by doing lots of math and queries inside the database, most of them just make two calls, one to sys.sysperfinfo and another to tempdb creation time, other than that, everything else is handled in the Python script. What you will need to do to prep your MSSQL databases for access from TCP/IP if you haven't already, and create an account that has at least SELECT access on tempdb and master (plus any other database you're trying to monitor.) that does not use Windows Authentication.

I found setting up MSSQL to allow access to non-Windows domain computers a bit of a chore, but I did manage to do it, so if you need/want help with that I can definitely help you with that. The best way to make sure the database will accept connections is to fire use one of the check plugins before using the wizard to ensure the Windows Server will accept the connection, soething like this:

/usr/local/nagios/libexec/check_mssql -H <your windows IP here, sometimes you'll need to include the instance too, example: 192.168.5.0\SQLEXPRESS' --port <your port, defaults to 1433> --username <username> --password <password>

Once that connects, that same information should allow the wizards to connect. I'm sorry if this is not news to you, just making sure. Please let me know if you have any questions at all!

The Server wizard is for measure general health of all databases, and I'm looking to put more specific metrics in it, so I would love to hear which metrics you find most relevant. Any criticisms, wants, suggestions, I'm thankful for you trying these out.

Currently, the per second analysis metrics are based off of database uptime, so the longer the database runs the less volatile those numbers are. I was debating changing that to much more in tune with current database behavior rather than total past database behavior. Would you think a per second analysis would be better if I took a shorter poll?

The Database wizard is more for individual database metrics.

The query wizard is for queries, and testing the query against a expected result, can be a string or number.

[desmondlewissmith]

Awesome, I'll get these setup this week and let you know how it works out.