The NSCA‑ng package provides a client-server pair that makes the Nagios command file accessible to remote systems. This allows for submitting passive check results, downtimes, and many other commands to Nagios or compatible monitoring solutions. It can also be used for implementing distributed setups. The submitted data is queued by the NSCA‑ng server if Nagios goes down. Multiple check results or commands can be submitted in one go, and multiline plugin output is fully supported.

The NSCA‑ng client (send_nsca) accepts all input, command line arguments, and configuration files accepted by the send_nsca binary provided with the original NSCA package. Python programmers can use the NSCA‑ng client module instead of the standard client. NSCA clients cannot talk to NSCA‑ng servers (nor vice versa), but NSCA and NSCA‑ng servers can happily run side by side.

NSCA‑ng also offers the following features:


Debian/Ubuntu Packages

Ubuntu users can install NSCA‑ng from the official repositories. An official Debian package is available in Jessie. Debian Wheezy users are encouraged to use the backport or the package provided by the Debian Monitoring Project.

For users of other Debian (or Debian-based) operating system versions, the following packages should work.

RedHat/SUSE Packages

Paul Richards and Gunnar Beutner created a SPEC file for building RPM packages. We used a slightly modified version to build the following packages.

OpenBSD Package

OpenBSD users can install net/nagios/nsca-ng from the ports tree.

Source Code

See the release history for a summary of changes between versions. A detailed change log is also available. Old releases can be found in the download area.

The files are signed using the NSCA‑ng developers key.


Git Repository

The NSCA‑ng source code is maintained in a public Git repository:

You can browse the repository online.

Bug Reports and Patches

Bug reports and patches can be sent to the developers list (no subscription required). The patch format created by git format-patch or git send-email is preferred. Alternatively, you could push your changes to a public repository and post the output of git request-pull (preferably with the -p flag) to the list. If you don’t like either method, feel free to contact me and we’ll sort something out.

Integration Tests

The development workflow includes continuous integration tests hosted by Travis CI and static code analysis performed by Coverity Scan.


Manual Pages

Further Documentation


There are two NSCA‑ng mailing lists.


Many thanks go to my employer, Zentraleinrichtung für Datenverarbeitung (ZEDAT) at Freie Universität Berlin, and especially to Heiko Schlichting, who contributed most of the good ideas behind NSCA‑ng.

Thanks also go to Alexander Golovko for contributing the NSCA‑ng client module for Python.