Is there any way to restore Nagios config from NDOUtils DB?

[iam33]

Hi!
Thanks in advance.

I´m probbing the NDOUtils and other 3th party tools and I don´t know if there is any way to restore Nagios configuration from data on NDOUtils DB....is it posible?

thanks!

[mcapra]

NDOUtils does not concern itself with Nagios configurations. It's simply a replacement for status.dat and event information that consolidates those things into a MySQL database for easy querying. It's all state/event information though, nothing directly related to configuration.

Nagios XI is the official enterprise solution for database driven configuration management.

There also exist a few other open source tools specific to Nagios:
https://github.com/indexzero/nconf
https://sourceforge.net/projects/nagiosql/
http://www.onecmdb.org/wiki/index.php?title=Main_Page
https://sourceforge.net/projects/lilac--reloaded/

And Chef/Ansible/Puppet all have Nagios based cookbooks/modules:
https://forge.puppet.com/thias/nagios
https://supermarket.chef.io/cookbooks/nagios
https://docs.ansible.com/ansible/2.6/mo ... odule.html

In which case your [Chef Server, Puppet Master, Ansible Tower] becomes your "configuration database".

[iam33]

thanks for your answer!!

I known that NDOUtils isn´t a tool to consolidate Nagios config in DB, but NDOUtils allow to save Nagios config into DB,maybe there is an procedure to do the revers process.... or other 3th party tool coul be do these....

Do you know what I want to say?

thanks!!

[mcapra]

but NDOUtils allow to save Nagios config into DB

Nope, it doesn't do that. If it did, you wouldn't need a separate database to have a configuration management utility. See NagiosQL, NConf, Lilac; They all have separate databases doing separate things from the NDOUtils database. The reason for that is because NDOUtils doesn't hold configuration information.

NDOUtils saves the status for each of your monitoring objects as well as the events occurring within Nagios Core. This may happen to also have some information that could be tied back to the configuration for that particular monitoring object (retry attempts, host name, service description, check command, etc), but the cardinality of the two data sets (status versus configuration) are uniquely different. You could certainly try to reverse-engineer your way from status to configuration, but it's always going to be an incomplete picture due to things like inheritance, wildcards, etc that exist in configuration sets but not in an object's status (because the Nagios engine figures all that stuff out auto-magically ahead of defining the status).

[scottwilkerson]

mcapra is correct, it does not hold any nagios configurations

[iam33]

thank you so much for your answers!!

[scottwilkerson]

thank you so much for your answers!!

Locking