Home
The goal of this project is to cross the bridge between IT operations staff that are using Nagios for systems monitoring and developers that create the applications that need monitoring.
In my entire professional life, I've never seen any developer actively contributing to a Nagios configuration. To me, that does not make sense as systems and application monitoring should be an integral part of the development cycle. As such, this should be a shared responsibility between IT operations staff and developers.
To accomplish this, we need to make sure that developers actually understand the Nagios configuration and feel comfortable contributing to it. What better way to do this than to turn Nagios configuration development into the same experience as developing any other application by using a present day technology stack and the same development best practices they are accustomed to.
That technology stack ended up being NodeJS+TypeSript, a custom CLI and Nagios running on Docker, hence the project title:
The project enables developers to run npm test and npm start like they would with any other application and have it validate the Nagios configuration and start a Nagios instance respectively.
Although the project is still in BETA, that goal has been met. If you're curious to start using this project, continue reading the Getting Started. For more advanced topics, see the Table of Contents in the sidebar 👉
A big shoutout to the development team of Guidion, which served as a guinee pig for this project. They provided real-life examples, good discussions on architecture and a clear direction on what a developer would expect out of working with Nagios.
Like any other tech company, they are always looking for good people. If you fancy working in an inspiring environment that incubated this project, check out their career site (sorry, dutch site only).
Made in Amsterdam with ♥
Special thanks to
