Projects

Icinga

Icinga is a monitoring system based on Nagios. It extends its capabilities and delivers new features like libdbi for database abstraction, well written APIs and a new, easy to extend webinterface.

Shinken

Shinken is a multiplatform (GNU/Linux & Windows) monitoring tool in Python compatbile with Nagios configuration and plugins. The main goal of the program is to allows users to have a easy administrable distributed and high availability monitoring tool. It scales the load by ... [More] "cutting" the user's configuration into independant part and send it to workers. It also have multisites features, UTF-8 names and is compatible with Nagios configuration and plugins. [Less]

collectd

collectd is a small daemon which collects system information periodically and writes the results to an RRD-file. What does collectd do? collectd collects information about the system it is running on and writes this information into special database files. These database files can then be used ... [More] to generate graphs of the collected data. collectd itself does not generate graphs, it only collects the data. You should use software like drraw to generate pretty pictures from these RRD-files. Nonetheless, sample scripts are included to get you started on own graphing scripts. [Less]

Opsview Core

Opsview Core is an open source network monitoring software application that solves the challenges of monitoring modern IT and network systems.

NSCP

NSClient++ (NSCP) aims to be a simple yet powerful and secure monitoring daemon for Windows operating systems. It is built for Nagios, but nothing in the daemon is actually Nagios specific and could probably, with little or no change, be integrated into any monitoring software that supports running user tools for polling.

check_mk

Check_mk adopts a new a approach for collecting data from operating systems and network components. It obsoletes NRPE, check_by_ssh, NSClient and check_snmp. It has many benefits, the most important of which are: * Significant reduction of CPU usage on the Nagios host. * Automatic inventory of ... [More] items to be checked on hosts. The larger your Nagios installation is, the more important get these points. In fact check_mk enables you to implement a monitoring environment exceeding 20.000 checks/min on the first hand. [Less]

GroundWork Monitor Open Source

A complete availability monitoring solution that ensures IT infrastructure uptime while identifying issues before they become real problems. Unifies proven open source tools - Nagios, Nmap, sendpage, PHP, Apache, MySQL and more - through PHP/AJAX-based components and an integrated user interface to deliver the extensible functionality you require.

Mod-Gearman

Mod_Gearman is an easy way of distributing active Nagios checks across your network and increasing nagios scalability. Mod-Gearman can even help to reduce the load on a single nagios host, because its much smaller and more efficient in executing checks.

nsca2

Note: I started this project out as "NSCA2". Community requested to rename as another thing to not cause confusion. So it got renamed to NRD: Nagios Result Distributor. This project is an attempt to overcome the actual Nagios NSCA protocol shortcomings: The motto of the NRD daemon ... [More] would be "distributed monitoring should not impose additional restrictions on the functionality of Nagios". The actual restrictions of using NSCA are: - Packet length limited: Data returned from plugins is tending to get bigger and bigger. Current NSCA truncates output of the plugin data. NRD should not be a limiting factor in the size of the output of a plugin, and should at least evolve with Nagios limits (so that there is no difference between using NRD or not) - No support for multiline output: Nagios 3 introduced multiline plugin output. NRD should support multiline plugin output. - Hostnames limited to 63 characters - Service names limited to 127 characters Enhancements - Timestamp from client. The NRD client will send the timestamp of execution of the plugin to the server, together with the result. This will impose a restriction of syncing clocks between master and slave servers, but really... your servers clocks should already be synched with ntp :) - Result queueing. If the NRD client cannot connect to the server, it will be able to spool results and send them when communication is possible again (because the timestamp is saved, the result can be injected later into nagios with the correct time). Although Nagios will discard results that are too old, maybe we can convince the Nagios developers to do something with them :) - Ability to set client allow / deny rules (as another access method) - Use of different encryption keys for different clients [Less]