Many people rely on Nagios XI for their monitoring needs, but what happens if the primary XI monitoring server goes down, crashes, loses power, or gets disconnected from the network? For example, if your border router or internet connection goes down, Nagios XI will be unable to deliver email alerts to admins. See below:
Continue reading ‘Monitoring a Nagios XI Server’
When monitoring your network environment, it is extremely important to receive email notifications properly. The Manage Email Settings page was created to allow you to manage these settings and ensure that Users are properly notified by the XI server.
You can manage your Nagios XI server’s email settings through the Manage Email Settings page located in the Admin panel. Your email settings can be configured either by Sendmail, or SMTP to transmit email Alerts and Notifications for potential infrastructure issues from Nagios XI to your Users or Contacts. The ability to use SMTP as opposed to Sendmail is particularly useful if you would like to add authentication via a SMTP relay to your outgoing Nagios XI mail.
The video tutorial below shows how email settings can be modified within Nagios XI.
The “Action URL” component has been quietly deprecated in favor of the newer “Actions” component. The “Actions” component has been released for some time now and has been rolled up into the base install of XI. Although it is most commonly used to add URLs to specific Nagios objects on the details pages in XI, it is by far more advanced than its predecessor “Action URL”. The “Actions” component is truly one of the more powerful components available for Nagios XI, on par with event handlers in extensibility and complexity.
The use cases for the Actions component are near endless. A simple example would consist of the streamlining of repeated tasks, like the adding of common comments to particular hosts. This can be accomplished using the Actions component and the command pipe. For the following example, we will assume that the comment to be added to a host relates to the completion of a successful security audit by the user “auditor”. This action will include the passing of the %host% macro to a script that will write to the Nagios command pipe.
First create a script named “security_audit_completed.sh” in /usr/local/nagios/libexec. The script follows:
/usr/bin/printf "[%lu] ADD_HOST_COMMENT;$HOST;1;auditor;This host has passed security audit\n" `date +%s` > /usr/local/nagios/var/rw/nagios.cmd
Continue reading ‘Unleashing the Power of Nagios — Utilizing the Actions Component’