Nagira -- Nagios RESTful API

Version 0.5.0

Build Status


Light-weight web services RESTful API for Nagios monitoring.

Source Code

Source code available from Github


As Docker container

To pull and run from public Docker registry run as:

docker run -d -p 4567:4567 -v /etc/nagios3:/etc/nagios3 \
  -v /var/cache/nagios3:/var/cache/nagios3 \
  -v /var/lib/nagios3:/var/lib/nagios3 ortym/nagira

As Ruby gem

    gem install nagira

For more details look at INSTALL


  1. Run Sinatra application nagira
  2. Use HTTP client to get information:
   curl http://localhost:4567/_objects/contact/_list

   curl http://localhost:4567/_status/_list

or to send check result to Nagios:

curl -X PUT -H "Content-type: application/json;" \
    -d @host_check.json

  "plugin_output" : "ping OK"

See more in FEATURES and API documentation in API

How and why?

Provide simple and consistent way for information exchange with Nagios

  1. Provide read-only access to the object configuration and object states by reading Nagios data files: status.dat and objects.cache, and
    • objects.cache file keeps information about Nagios configuration (lists of servers, services, groups etc);
    • status.dat file is file that stores information about current state of the objects (hosts and services) and Nagios process itself;
    • Nagios configuration information is in nagios.cfg file, by reading and parsing this file all other configuration can be obtained.
  2. provide check result submission interface (similar to Nagios NSCA and for setting/updating Nagios configuration.

File parsing is implemented in the background thread on a regular intervals, so that parsed information is available immediately when HTTP request comes.


YARD documentation included with the project, run yardoc in project root directory. Generated YARD docs are available at

Unformatted Markdown file in the project's docs directory.

API Documentation

API endpoints are partially documented in the inline comments and accessible in YARD documents (Nagira class), most of the enpoints are documented in API.


Dmytro Kovalov,

2011, Dec, 26th - started




If you want to contribute feature, send a bug fix, or simply report a bug or requet a feature see CONTRIBUTING.