Search:

Hello again dearest Google bot! Today I have a pretty big announcement for all you 0.4.0 waiters out there. I have release another nightly build which is the result of a lot of work put in during august. The main new features is of course the new protocol as well as a very extended PythonScript module. Since there is so much new it is a bit difficult to create s short blog post to summarize the new features. But I hope that the new test.py and test_pb.py scripts will eventually cover most of the features if nothing else as a test script. == Installing Scripts == The best way to get start with these scripts are to "install them". Something which is now supported from the command line lik so:

This is a pretty complicated command actually. The first thing we do is add '''--client''' which runs command line queries as well as commands on modules without launching NSClient++ in server mode. IN essence this is the "offline mode". Then we have '''--module PythonScript''' which tells the "client" to load the PythonScript module (regardless of what your configuration says) this also prevents any configured modules from being loaded. The next step is the '''--command execute-and-load-python''' which actually just sends a command down the pipeline to see if any plugin want to run it. In this case the PythonScript module will run it and do so by executing the '''---script test.py''' script. This script is then the magic, if we look at the __main__ function of this script we can see the following:

The interesting thing here is that we have a python script which is modifying our configuration by first enabling the PythonScript module (using an alias: pytest) and then adds the relevant script (again with an alias pytest). The reason for using the alias is so we can easily "uninstall" this without messing up your configuration. This is thanks to the new fully supported multiple module support. Now unfortunately NSClient++ does not (yet) support uninstalling but that will come. The next step is (as the install command above will tell you) to reun the test script from the "test mode". == Test mode == Test mode is nothing new since as far as I can remember it has been possible to run NSClient++ is "test mode" previously we used -test and for 0.4.0 we use

nscp --test

This will start NSClient++ like a service with three main exceptions: 1. The program will run with '''YOUR''' privileges and in '''YOUR''' session (not system) 2. The program will run with console log and debug log enabled 3. You will be able to interact with NSClient++ directly So lets try it out.

This is a big chunk of output and unfortunetly we get a lot of debug output here as well, some day I shall improve this to list all relevant output at the end. But the interesting tidbits (cleaned up below)

And as we can see all tests but one succeeded and that is a but I shall fix at some point. When you only have a warning threshold and no critical threshold the warning one is discarded in the parser. Now the cool thing is that this all work the same from linux... and with the right setup and some tinkering... remotely... pretty cool huh? // Michael Medin

I am looking for people interested in distributed monitoring! As some of you might know I am building some features do manage distributed and incoherent monitoring (ie. more then one monitoring tool) so I am interested in getting some real world insight into this area. So if you or anyone ...

First off Linux seems to be doing great most features just works and thus far I am pretty impressed with the "portability". I have written a page on how to build on Linux if you want to try it out for your self [wiki:build/04x/linux]. The new nightly ...