A Page in: About NSClient++. Fixed debian builds * NSCA Client: Fixed # nsca status can be set with a . This document describes the procedures for installing Nagios monitoring agent, NSClient++, on a target Microsoft Windows desktop or server for the purposes of . A Page in: About NSClient++.
Welcome to NSClient++ - NSClient++
Nsclient++ Support Library Project Exchange. Home Directory About. Search Exchange Advanced Search. Search All Sites. Nagios Live Webinars Let our experts show you how Nagios can help your organization. Register Now. Contact Us Phone: Login Username. Remember Me. Nagios, the Nagios logo, and Nagios graphics are the servicemarks, trademarks, or registered trademarks owned by Nagios Enterprises.
All other servicemarks and trademarks are the property of their respective owner. The files and information on nsclient++ site are the property of their respective owner s. Nagios Enterprises makes no claims or warranties as to the fitness of any file or information on this website, for any purpose whatsoever. In fact, we officially disclaim nsclient++ liability. We do, however, think these community contributions are pretty damn cool.
If you have other protocols or monitoring solutions the general concepts can be easily adapted to any of the other supported protocols. But currently most modules are Windows only thus the benefit on other operating systems are limited.
We do recommend that you do nsclient++ skip this step, as you will have issues later and get frustrated… What is 15minutes compared to a great monitoring solution? But for the reminder of this tutorial we nsclient++ consider ini files since it is the normal and simplest way. To edit it you can use any text editor such as notepad. Also note that on Windows after Vista the ini file is residing nsclient++ a protected space and nokia x101 themes you need to launch nsclient++ editor as administrator to edit the files.
To make you configuration you first need nsclient++ decide which modules you want then and nsclient++ each one of them in nsclient++. We nsclient++ start the nsclient++ why by presenting the various modules you can use and covering how to configure some of them. Here are the available modules. Each module get loaded if enabled. You can enable all and use only one, but that may open doors for nothing and add load on your systems.
There are nsclient++ few ways you can enable modules, setting the value to 1, true and enabled are all correct but enabled is preferred like so:. There is an advanced topic when it comes to modules and that is loading the same module multiple times.
This is not common but since it changes the syntax we nsclient++ it for completion. When a module is loaded multiple times nsclient++ is given an alias as a key since key names have to be nsclient++ and thus the syntax changes into this:. This is nsclient++ only difficult part. We will cover here the most needed modules, which are in bold in previous chapter.
If you omit some settings per protocol, default values nsclient++ be used. Here are the recommended default value section:. Thus you need to enable some form of communication with nsclient++ central server. Transports are methods which facilitates communication between Monitoring server and your server.
They both support transferring files but they have slightly different approaches so things work differently but the end result is nsclient++ same. A file gets transferred. In our case the end result is that a monitoring result gets submitted to Monitoring server. All you need to configure is who is allowed to connect as well how to handle arguments. The drawback to not allowing argument is that you need to configure everything in nsclient. The other option is to allow arguments nsclient++ it is important to consider the security implications before doing so.
A less restrictive configuration is shown here where we have allowed all kinds of arguments for simplicity. Another way to configure nsclient++ is to use what is commonly referred to as passive monitoring. This can avoid a lot of load by not polling for nothing. Load is also distributed on all nsclient++ and not Nagios centric. Alias allows you to nsclient++ commands nsclient++ by preparing command line with both dynamics and static arguments.
Event-logs are a great source of information for monitoring. Allow real-time monitoring and extended filtering. As the subject itself is a bit complicated, start basic by grabbing all and exclude after. By default, the Windows service run as Local System. Needed right will depend on what you want to monitor, but as a basis, you will need an account: Needed to collect performance counters - Log nsclient++ as a service grant.
Granted when you set the account, but should be applied through GPO to remain consistent. Power users group nsclient++ a no go, it still nsclient++ but does nothing nsclient++ vista and upper.
On XP andit nearly means admin right, which is nsclient++ to the target. Encryption depend heavily on which communication protocol you need. This add security to firewall rules, by also restricting access within the same network. Table of nsclient++ How it works Requirements Windows: Danger We do recommend that you do not skip this step, as you will have issues later and get frustrated… What is 15minutes compared to a great monitoring solution? Note Modules in bold below nsclient++ commonly used with Nagios Nagios.
Note This is the only difficult part. Danger This has security implications! Note Event-logs are a great source of information for monitoring.