opsi manual opsi version 4.0.2 - opsi Download - uib

opsi manual opsi version 4.0.2
Check: opsi-check-diskusage
156 / 193
This check monitors the usage of the resources (directories) which are used by opsi. The following table shows the
resource names and the corresponding directories:
Table 8: opsi resources
Resource name Path
/ /usr/share/opsiconfd/static
configed /usr/lib/configed
depot /opt/pcbin/install
repository /var/lib/opsi/repository
Please note that this check monitors only opsi relevant data and do replace a general disk usage check for the server.
The following command retrieves all resources at one time:
check_opsi -H configserver.domain.local -P 4447 -u monitoring -p monitoring123 -t checkOpsiDiskUsage
In addition to this standard variant you may restrict the check to the resource depot:
check_opsi -H configserver.domain.local -P 4447 -u monitoring -p monitoring123 -t checkOpsiDiskUsage -r depot
The default result value of this check is OK and the free space of the resources. The free space is given in Gigabyte.
The default values for the Warning and Critical results are:
• WARNING: If at least one resource have 5GB or less free space.
• CRITICAL: If at least one resource have 1GB or less free space.
This are the default thresholds. They may changed by giving other values for Warning with the -W or --warning
options and for Critical wit the -C or --critical option. With these options you can give the thresholds as Gigabyte
(G) and as percent (%) as well. The produced output uses the same unit which is used to define the thresholds.
Finally an example:
check_opsi -H configserver.domain.local -P 4447 -u monitoring -p monitoring123 -t checkOpsiDiskUsage -r depot --warning\
10% --critical 5%
Check: opsi-client-status
One of the targets of the opsi Nagios connector is the software roll out monitoring by viewing to single clients. This
is one of the checks which is designed for this job. More exactly: the software roll out and last seen situation of a
certain client is checked.
The result of the following checks is determined by two different states:
• The roll out state of one or more software products:
The software roll out state results to:
– OK if the software is installed at the in the same product and package version which is available at the server
and no action request is set.
– Warning if the software is installed in version that is different to the servers version or if any action request is
set.
– Critical if there is a failed reported by the last action.