NagiosXI and AzureDevOps

[ghosham]

Hello,

We have recently procured NagiosXI license and were told we can have 3 machines as part of this license: Production, Backup and Development.
I want to setup a CI/CD pipeline using AzureDevops such as every time, I make a configuration change at Dev server, it should copy the latest configuration to Prod and Backup server and restart the nagios service so that the new check can take effect at Prod end.
Has anyone achieved this earlier? would like to get some insights..

[benjaminsmith]

Hello @ghosham,

There are a couple of options, if you are making simple changes using the REST API, you could just point those changes at both systems. However, If you want to sync everything, the easiest method is to use the backup and restore feature (e.g run the backup on the dev and restore this to production). Of course, you would want to be cautious about making changes to dev If they are frequently synced.

Backing Up And Restoring Your Nagios XI System

Let me know if that helps and if you have more questions.

Benjamin

[ghosham]

Hi Benjamin,

Not exactly what I am looking for. I was hoping if I install git and use /usr/local/nagios as the repo local directory at Dev server and same directory as repo remote directory on Prod server; any changes under that local directory can then be pushed to prod using git push origin master. Shouldnt this still hold out?

The backup and recovery option is good, but its a manual process. Interested to know about REST API, if you could give more information around that as well.

[benjaminsmith]

Hi @ghosham,

The way Nagios XI handles configurations is by writing out the information stored in the CCM database (nagiosql) Each Nagios server contains a separate database with the current, running configurations. Any changes in the CCM are written out as the configuration files to the directory, Nagios Core is re-started and then this data is imported into memory. It's not recommended to sync the XI configuration directory as the systems databases would likely not be the same.

A workaround would be to use the static directory in XI. Assuming there are no errors in the configurations, you could pull those files into the XI static directory. However, you would not be able to edit anything in the CCM on the production side.

See: Nagios XI Manual Config File Management

As far as the API goes, it is fully documented in the Nagios XI interface, go to Admin > Help to view.

[ghosham]

This is no longer a requirement. Please feel free to close the thread.

[scottwilkerson]

This is no longer a requirement. Please feel free to close the thread.

Great!

Locking thread