This document describes how to automate adding and removing hosts and services in Nagios XI from the command line. Some administrators may have need to automate the process of adding and removing hosts and services in Nagios XI for use with cloud computing or large environments where solutions like Puppet or Chef may already be implemented. The procedures below outline how administrators can create their own automation solutions to safely add and remove hosts and services in Nagios XI while still maintaining the integrity of the monitoring environment.
Archive for the 'Deployment' Category
We have now released a CentOS 6 version of Nagios XI in the Amazon Ec2 for cloud monitoring. The new release is build on the x86_64 architecture and will be the standard for future builds.
In case you missed the announcement from Amazon, all instance sized can now be spun up with 64 bit images. This is a great step forward as it allows someone to start with a small instance at a much reduced price and as they grow they can take their same snapshot an start it up on a much larger system.
More information about running your Nagios XI system in the cloud can be found in our Nagios on Ec2 article in the Nagios Exchange.
The
latest Nagios XI – Amazon Ec2 cloud images have been pushed out to the following additional location:
- S. America (Sao Paulo)
The Nagios XI cloud images are an excellent opportunity to try Nagios XI without having the upfront expense of dedicated hardware and can be upgraded with virtually zero downtime.
Additional documentation on using the Amazon cloud images for your Nagios XI deployment may be found on the Exchange.
Using Nagios XI In Amazon EC2 Cloud
Now available 2 new clients to send passive check results to Nagios Remote Data Processor (NRDP) server.
We have just released:
send_nrdp.sh Bash NRDP Client
send_nrdp.py Python NRDP Client
You no longer need to install PHP or Perl on your client machines to run passive checks with NRDP. Both of these implementations can accept result piped from STDIN and you can change the delimiters to whatever you like.
STDIN results should be in the following order, for HOST checks:
HOSTNAME STATE OUTPUT
for SERVICE checks
HOSTNAME SERVICENAME STATE OUTPUT
Additionally, the bash version can take an XML file of check results formatted like so:
<?xml version='1.0'?> <checkresults> <checkresult type="host" checktype="1"> <hostname>YOUR_HOSTNAME</hostname> <state>0</state> <output>OK|perfdata=1.00;5;10;0</output> </checkresult> <checkresult type="service" checktype="1"> <hostname>YOUR_HOSTNAME</hostname> <servicename>YOUR_SERVICENAME</servicename> <state>0</state> <output>OK|perfdata=1.00;5;10;0</output> </checkresult> </checkresults>
The latest Amazon Ec2 cloud images have been pushed out to the following additional locations:
- Asia Pacific (Singapore)
- Asia Pacific (Tokyo)
The Nagios XI cloud images are an excellent opportunity to try Nagios XI without having the upfront expense of dedicated hardware and can be upgraded with virtually zero downtime.
The Nagios XI ec2 cloud image is now available in the following regions in 32 and 64 bit versions:
- US East (Virginia)
- US West (N. California)
- EU West (Ireland)
Additionally, the new version will automatically install the latest Nagios XI when if is first booted. This will eliminate the need to change AMI ID’s when new version come out. While it is convenient to not have to lookup the AMI ID, please be aware when you first start your instance the current version of Nagios XI is installed and compiled at boot. This will take at least 15 minutes before the instance will become available. The amount of time will depend on the instance size you create.
Another change was made to meet Amazon security guidelines and now all instances have an ec2-user account to be used for ssh access. This user has full sudo access and will login with a key pair as usual.
Additional documentation on using the Amazon cloud images for your Nagios XI deployment may be found on the Exchange.
Many customers showed interest in deploying NSClient++ to multiple machines across a windows domain, without the need to log in remotely or be physically present on these machines.
If you are using Nagios to monitor a windows environment, you can use FTP as a component to deploying NSClient++. We just posted a document on the Nagios Library, which explains how to configure FTP for Nagios. You can review it here.
Additional information on deploying NSClient++ via FTP in Nagios will be available soon.
Managing a Nagios XI server is an important requirement to ensure that the monitoring server can be configured to meet organizational needs and that application updates (patches and upgrades) can be applied. Nagios XI servers that are placed on remote networks often requires that an administrator configures firewalls and routers to allow access to management features.
We wrote a short document that describes the requirements for and methods of managing remote Nagios XI servers. To learn more, read the document on Nagios Exchange.
Large scale monitoring of Windows desktop/server environment made easy using Nagios XI, NSClient++ and Microsoft SCCM.
NSClient++ SCCM Package
NSClient++ Agent install pending
Continue reading ‘Deploy NSClient++ Agent using Microsoft’s SCCM with Nagios’
