opsi manual opsi version 4.0.2 - opsi Download - uib

opsi manual opsi version 4.0.2
160 / 193
check_opsi -H configserver.domain.local -P 4447 -u monitoring -p monitoring123 -t checkPluginOnClient --plugin "C:\\\
opsi.org\\nagiosplugincol\\check_win_disk.exe C:" -c client.domain.local
This call checks the client client.domain.local. At the client the plugin check_win_disk.exe is called with the
parameter C:. This means, that the hard drive with the letter C should be checked. The output and the result value
of the plugin will be fetched by the opsiclientd and will be given back to the Nagios server (via the opsi server) in a
for Nagios correct format.
Another special feature is to hold the last check results, even if the client is not reachable.
This feature was implemented according to the fact that desktop clients not always are running like servers, but the
most time in their life are usually switched off. Normally Nagios will show for switched off clients the result Unknown.
In fact the most problems on the monitored clients will not disappear by just switching them off and on again. So
the information that a client had a problem before it was switched off may be an essential information for the system
administrator. (You may try to solve this problem by using Timeperiods at the Nagios configuration, but we think
that this is not flexible enough and leads to a permanent configuration work). So this opsi extension give you the
possibility to give back the last real check results if the client is not reachable right now.
In order to use this feature, you have to use the Nagios macros $SERVICESTATEID$ and $SERVICEOUTPUT$.
$SERVICESTATEID$ gives the last result value and should be passed to the -s Option. $SERVICEOUTPUT$ gives the
last output line and should be passed to the -o Option. So check can give these last values instead of Unknown if the
client is not reachable.
check_opsi -H configserver.domain.local -P 4447 -u monitoring -p monitoring123 -t checkPluginOnClient --plugin "C:\\\
opsi.org\\nagiosplugincol\\check_win_disk.exe C:" -c client.domain.local -s $SERVICESTATEID$ -o $SERVICEOUTPUT$
20.5 opsi monitoring configuration
This chapter focuses on the configuration that have to been made for a working interface between the opsi and the
Nagios server. Just see this as a recommendation, there will be a lot of other ways to do the job.
This description uses a Nagios server as monitoring server. On a Icinga server it should work very similar but you
have to change some path entries. It should also work on other Nagios derivatives but this is not tested.
Tip
The configurationfiles from these Chapter are in opsi-nagios-connector-utils svn-Repository. To get these example configurationfiles
you can connect over a browser to following url:
https://svn.opsi.org/listing.php?repname=opsi-nagios-connector-utils
or you can make a direct checkout from repository with following command:
svn co https://svn.opsi.org/opsi-nagios-connector-utils
20.5.1 opsi monitoring user
In monitoring environments you will often find that the access is just restricted by IP numbers. Because of the lack
of security of this solution we decided to work with a real user / password security in this opsi extension.
Using the opsi standard group opsiadmin would give the Nagios more rights than needed. So you have to create an
own opsi user for the opsi-Nagios-Connector.
In the following example a user named monitoring with the password monitoring123 is created for opsi:
opsi-admin -d method user_setCredentials monitoring monitoring123