A tutorial for writing a quick and simple Lua script which will turn check_cpu into a multi functional check which return top CPU consumers. In last weeks edition I introduced the various parts we need to make this a reality. And that idea I have with NSClient++ is to create a Lego box with small multi purpose functions which the users can combine in many different ways. Here I will show you how we can do that.

An often requested feature is to include the top-5 consumers of high CPU load in the result from check_cpu (or checkCpu). I have often discarded this as a non-core feature since it is not something I think should be part of NSClient++ instead I think it should be a script. Since no-one has created such a script I figured it would make a nice blog post so here I describe in a step by step guide how to create such a script for NSClient++.

This is a YouTube video from my presentation at OSMC this year. The good folks over at Netways kindly allowed me to post the video here on my blog.

As always I really enjoyed the conference as much as the social aspect of it. It truly is one of the best conferences in the field. This was my sixth year which as I noted earlier started out a bit weird. I will not cover the limousine story here again instead this is purely about the conference.

The conference started off with the usual introduction by bernd who did it in English this year which I think was nice but quite frankly the usual “food is in the food area” and “conference is in the conference are” I can pretty much understand even in German. As I only speak English I will, as usual, only cover the English track here.

Well, this is an odd post. I find it difficult to start to be honest. How do I write about my adventures without it sounding strange or bizarre? But perhaps it needs to sounds bizarre for that was how it felt to me. I know this is all a gag but it is interesting how well my mind failed to understand that at the time.

A lot of people coming to NSClient++ has a background in NRPE since it is a common transport mechanism for check results on Linux.

And while NSClient++ is fully NRPE compatible it allows for more control and has more features which can make it seem difficult to get started with. This is a guide for getting started with NSClient++ from a NRPE perspective.

Just thought I'd drop a short note mentioning my presentation for NWCNA 2013 has been accepted and I will be presenting there.

The talk is (surprise surprise) about the new features of NSClient++ with a heavy focus on the up-coming 0.4.2 version which will take real-time monitoring to a whole new level.

I attended the conference for the third time and as always the weather in Bolzano in conjunction with a nice conference made for a great time. I have already mentioned my experiences with the hotel in a previous post so here I will focus mainly on the conference itself and my trip.

The biggest reason for Nagios success is the ability to extend it with custom scripts which makes it one of the most powerful monitoring systems. Now Nagios is not the only place where you can extend your monitoring! NSClient++ provides many ways to extend it with scripts and since I have gotten many questions about how to use scripts with NSClient++ lately I have decided to write this tutorial to help sort out the concepts.

NSClient++ despite its name is most often used in server mode responding to remote calls via either NRPE or check_nt. The closest thing to a client we get in normal mode of operation is NSCA where we submit data back. But NSClient++ can act as a client as well which is not just something I use for unit testing but something which can actually be useful in your monitoring environment.