WebReboot® Nagios® Plugin
Product Features
- Monitor your network in ways never before possible
- Automate corrective actions
- Download for free
Features
On its own, Nagios provides the ability to monitor a wide range of services and perform automated corrective actions or raise alerts based on those monitored events. The WebReboot Nagios Plugin adds new checks and corrective actions. A summary of the features follows with a set of screenshots detailing the user interface. You can also read the Getting Started Guide for more in-depth detail of any given feature.
Monitor events with the WebReboot Enterprise
Check if a host is powered on
Out of the box, the only way Nagios can check the status of a host is by performing some sort of network-based activity -- normally a ping. The problem with this approach is that you never know if the server is on and simply not responding to network requests or if the server is truly off.
The WebReboot Enterprise can monitor your host's actual power state. As such, the WebReboot Nagios Plugin can check whether or your server is powered on or off and trigger an event handler if it is off.
Check if host temperature exceeds warning and critical thresholds
Many servers do not have an easy means of indicating their temperatures. Those that do often only report the CPU temperature, without regard to the ambient temperature of the server. The WebReboot Enterprise can monitor temperature via a WebReboot Advanced Server Card. This card can report the ambient temperature of a server, which is a better indicator of overall server heating issues. For example, if an air conditioning units stops working, the server's ambient temperature will raise much more quickly than its CPU temperature will.
Corrective actions that can be performed by either the WebReboot Enterprise or WebReboot 3.0
Power on a device
Just as Nagios has no means to check the power state of a server out of the box, it has no means to power on a server. The WebReboot can, however, and using the power_on_host event handler, you can configure Nagios to power on a host whenever it is determined to be off.
Power off a device
On occassion, it is necessary to turn a host off. For example, the temperature may be too hot and the host must be turned off to prevent damage to the hardware. In these cases, the host can be shutdown properly at a software level. There are other cases, however, that require a hardware shutdown. For example, if a host is compromised and a rootkit is installed that prevents remote logins, it may be necessary to shut that machine off. This is a feature that Nagios cannot provide out of the box, but when used in conjunction with the WebReboot, can.
Reboot a device
Oftentimes, the best corrective action that can be taken is to reboot a host. This can typically be performed via a service or operating system mechanism. If, however, the remote access service is unavailable or the operating system has crashed (e.g., kernel panic or "blue screen of death"), then the only way to reboot the server is via a hardware reset. The WebReboot can provide this hardware reset that would otherwise be unavailable to Nagios.