Upgrading to Nagios Xi 5?
If you are using Nagios XI 2014 or later, you can upgrade your Nagios XI instance easily from the web UI, provided your server is connected to the Internet.
Upgrade Nagios XI From Web UI
Here’s how you do it:
From the Nagios XI web interface navigate to the Admin menu, click Check for Updates menu on the left, then click Check For Updates Now. If an update exists, the most recent version will be displayed and you can click the Upgrade to Latest Version button to start the upgrade process.
Note: If you are running the most current version, the Upgrade to Latest Version button will not be displayed.
Continue reading ‘How To Upgrade Nagios XI From Web UI. (How to Upgrade to Nagios XI 5.)’
The JSON CGIs, from the JSON branch of core, have been officially released with Nagios Core 4.0.7!
The original design goals were:
- To provide all information available in current CGIs in JSON format.
- Place the presentation responsibility on the client to minimize network traffic and server load.
- Perform operations on the server side that are significantly more easily done there.
- Spark community developers to create new Nagios Core UI’s from the easy to work with JSON from the CGIs.
The three new CGIs are:
- objectjson.cgi (object configuration)
- statusjson.cgi (status information)
- archivejson.cgi (historical logs)
Additionally, a new web app is included – jsonquery.html & jsonquery.js. This is a small UI for crafting GET requests, it can be used to trial specific parameters for GET requests, or to just explore the api. It is also the easiest way to get acquainted with the new CGIs.
Continue reading ‘Exploring the New JSON CGIs in Nagios Core 4.0.7! (Part 1)’
Nagios V-Shell 1.9 includes major performance updates, and a re-implementation of PHP caching that should decrease V-Shell page load times anywhere from 40-75%. I ran some benchmarking tests on a test system(Dual core desktop with 4GB of RAM) with 1800 hosts, and 7200 services. This system runs with an average CPU load of 2.0-6.0 throughout the day, so the hardware is being pushed pretty hard already from the check load. V-Shell 1.8 created page load times anywhere from 18-28 seconds throughout the interface without APC caching enabled. Needless to say, this is problematic for many users with larger environments. The Core cgi’s were able to load anywhere from 2-11 seconds, with the service status page taking around 9-11 seconds to load all of the data. My goal for 1.9 was to minimize any unnecessary processing, and optimize any functions that were inefficient or using slower PHP built-in functions. The differences in 1.9 are substantial. Without any caching enabled at all, I was able to decrease the average page load time to 9-14 seconds, which is 40-50% faster by itself. Once I had the code optimized, I reworked the APC caching functionality. If a user has PHP’s APC caching packages installed and enabled on their web server, V-Shell will cached the objects.cache file until it detects any changes in the file, while the data in the status.dat file will be cached based on a TTL (time to live) config option which now exists in 1.9. Once the data is cached in APC, the page load times throughout the interface averaged between 4-5 seconds for all pages, which is a 75% decrease in load time on average.
My goal for the next version of V-Shell is to add support for mklivestatus and ndoutils for backend data, which will eliminate the need to parse the objects.cache file and status.dat files for systems with those backends. This should further improve performance for larger installations.
Download Nagios V-Shell 1.9