Nagios XI Web Service Interface

[mp4783]

Does anyone know of any effort, either in the community or within Nagios, to develop a web service (REST/SOAP interface) front end for Nagios XI?

Specifically, an interface that would permit queries for information as well as provide configuration management functions such as adding hosts and services, configuring hosts and services, etc. Essentially, I'm looking for a web service API that extracts as much of the command line and/or Nagios XI GUI functions as practical.

The reason I ask is we need something like this and don't want to build it if someone has already done this or Nagios itself has it on their development map. I don't want to devote months of effort only to find that we reinvented the wheel.

Thank you.

[daveinvb]

Have you looked at these?

https://exchange.nagios.org/directory/Addons/APIs

[mp4783]

There are several options here, none of which are complete. Unfortunately, I don't believe any are designed to work with Nagios XI.

Direct manipulation of the configuration files works great for Nagios core, but it cannot be across-the-board for Nagios XI because of the back end databases.

Thanks for the suggestion as some of these might well provide ideas or "starter code" for a Nagios XI implementation.

[abrist]

Also, don't forget about the cmd.cgi and the json cgis. This should get you everything (status and config output, historical data, and object/process commands) other than a RESTful object configuration API.

[mp4783]

We would plan on using all existing tooling to abstract the function out to web service interface.

The real challenge is configuration control. My own on-going development of a mass configuration utility (some pieces are completed), give me direct experience with how challenging this can be.

[tmcdonald]

It's certainly something that has been discussed in the past, and if there is enough interest a feature request may have a good chance of being implemented. I don't see one in our internal feature tracker - would you like me to make one?

[mp4783]

You don't need to create a tracker unless you wish to. I just didn't want us to recreate something you guys were working on already. We will proceed with our own development.

Thank you.

[tmcdonald]

I'll close this up now, but keep an eye on the release notes for any API-related activity.