Hello,
I have 2 questions regarding database monitoring:
1. (Oracle) Is there any reason that check_oracle_health plugin is outdated? Its version is 1.7.3 (I'm using Nagios XI 5.2.0). According to this page https://labs.consol.de/nagios/check_ora ... index.html, current version is 2.1.1. => plugin version in current version of Nagios XI is 4 years old. If possible, I'd suggest update that plugin to the latest version as soon as possible. (I can do it myself in my installation of XI, however I believe other customers will appreciate that too.).
And maybe there are more plugins that should be upgraded...
2. (DB2) Are there any plans to create configuration wizard for monitoring IBM DB2 databases? If not, I'd give a chance to this plugin: https://labs.consol.de/nagios/check_db2 ... index.html. If you have any experience with this plugin, I'd appreciate all tips and cautions...
Thank you.
database monitoring
-
jdalrymple
- Skynet Drone
- Posts: 2620
- Joined: Wed Feb 11, 2015 1:56 pm
Re: database monitoring
1) It's a matter of priority. To upgrade to the latest plugin always require that the plugin is compatible with our predefined services, commands, wizards, etc. For XI5 the focus was on the heavy hitters - Windows and Linux. Is there any compelling reason for us to upgrade to the latest plugin? You have to remember we're just developers and support folks, we don't actually use the stuff so we rely on you guys to tell us the shortcomings we need to handle. We assume the general mass would prefer to see us focus our time on Windows Servers than on the Oracle client.
2) Kind of the same answer as before, and this one even moreso niche. The other problem with this one is that we don't have db2 installed anywhere in house to test against.
I do wish we had a wizard wishlist so that the developers didn't have to rely on their own best judgement as to what contributions would benefit the product the most. Unfortunately there are only so many hours in the day.
2) Kind of the same answer as before, and this one even moreso niche. The other problem with this one is that we don't have db2 installed anywhere in house to test against.
I do wish we had a wizard wishlist so that the developers didn't have to rely on their own best judgement as to what contributions would benefit the product the most. Unfortunately there are only so many hours in the day.
Re: database monitoring
Thanks for insight into your work. After years of working with nagios, I think you've done great job in monitoring Windows and Linux. But when I look at database wizard list - there are wizards for every major database engine, but one - IBM DB2. Try to ask your marketing dept. - maybe they will like the idea to announce support for all major databases (this might be interesting especially for large companies).
...and reasons to upgrade plugins - bug fixes and additional options/features(this may lead to decreased number of support issues and thus happier customers
).
But to make this thread more informative also for others, I've got a question: If, in general, there is an updated plugin that is used by XI, what option do you recommend:
- to replace existing plugin binary by the new one, or
- to create new command for that new version of plugin?
I suppose there may be problems when you decide to update some plugin in one of future versions of nagios, but that plugin was already updated by customer... On the other hand, new command will not be used by standard wizards... What's your thoughts on this?
Just one more idea: what about creating some site, where customers would place their ideas for improvement and other customers will be able to vote(one click) and comment these ideas. This gives you better feedback from community and you'll have list of features that are needed most...
(I've seen another software vendor to use this system).
...you're right - days should have many more hours
...and reasons to upgrade plugins - bug fixes and additional options/features(this may lead to decreased number of support issues and thus happier customers
).But to make this thread more informative also for others, I've got a question: If, in general, there is an updated plugin that is used by XI, what option do you recommend:
- to replace existing plugin binary by the new one, or
- to create new command for that new version of plugin?
I suppose there may be problems when you decide to update some plugin in one of future versions of nagios, but that plugin was already updated by customer... On the other hand, new command will not be used by standard wizards... What's your thoughts on this?
Just one more idea: what about creating some site, where customers would place their ideas for improvement and other customers will be able to vote(one click) and comment these ideas. This gives you better feedback from community and you'll have list of features that are needed most...
(I've seen another software vendor to use this system).
...you're right - days should have many more hours
Re: database monitoring
Generally it's best to upgrade if you have a need, like hitting a bug or something that would be resolved by a later version. This should always be done on a test system first to see if it will have any impact on the wizards and your current checks that use that plugin.
I personally would replace it, but only after knowing that it's fully tested in my environment so that it would work with the wizards. Again, you'd just have to be mindful of XI upgrades that could replace it.
I personally would replace it, but only after knowing that it's fully tested in my environment so that it would work with the wizards. Again, you'd just have to be mindful of XI upgrades that could replace it.