Documentation
Job-Check
Checks for jobs in a specific state (failure, error, dead, ...).
Usage
$ check_netapp_pro.pl Job -H <host> [--category=<cat> | --type=<typ>] [...] [--help]
Description
This plugin reads the present list of jobs and alarms if jobs matching given criteria were found.
Jobs can be filterd by:
- name (--include/--exclude=regex)
- category (--category=
) - type (not implemented yet)
- vserver (--vserver=
)
The category and type of a job are printed to the terminal in verbose mode (--verbose
).
Perfomance Data
The perfdata shows the number of queued jobs per node. See the output on examples below.
Configuration Sets
The check can either be configured on the commandline or by pointing --config
to a
file with a predefined set of commandline arguments (e.g. --config=JobSnapMirror.set
).
We deliver several of such sets for different purposes like the monitoring of SnapMirror Jobs. These files can be used as they are but also as template for your own predefined sets.
Where to store set-files
Set-files with no leading slash are expected to be in ./config
wheras a file-name
prefixed with a slash is considered to be an absolut path (e.g.
/usr/local/nagios/config/my.set
).
We recommend to save your own set-files outside of the check_netapp_pro/scripts
directory, so that your set-files survive the next update.
Mixing the config-set and commandline-arguments
Commandline arguments can be used together with a config-set file and will in case of a conflict overrule the arguments in the set-file. Keep in mind, that command-line arguments which can be repeated won't conflict with a second argument of the same name and therefore will be amended and not overruled.
E.g. Having category : VOPL
in the set file and --category=Certificate
on the
commandline, will result in checking all jobs of both categories because --category
can be repeated.
Also the definitions of the state-evaluation is tricky as the same state can be both in warning_state and in ok_state. This can happen either on the commandline, or in the config-set or as the result of mixing them.
E.g. --ok_state=paused
and --warning_state=paused
will result in a WARNING for any
paused job (WARNING wins over OK). This logic does not depend on where (config-set or
command-line), or in which order, these states are defined.
Simple Examples
Check all jobs as defined in the default set (./config/JobDefault.set
). Show the number of queued jobs per node in the perf-data section.
Check all jobs which have the string 'protection' in their name. Evaluate as defined in the default set (./config/JobDefault.set
).
Check all jobs which are in category VOPL. Evaluate as above.
List all jobs together with their category and type.
Checks all jobs in category VOPL on vserver srv01a.
Advanced Examples
Hint: The input for advanced examples is shortend. Replace the '...' below with ‑H <your filers ip or host-name>
Check all jobs which have the string 'protection' in their name. Exit critical if their state is neither success nor running.
Check all SnapMirror-jobs, alarms if state is not dormant, success, ... .
Same as above but uses a predefined (and editable) config-file.
Same as above but sends a warning when the job is running (because commandline arguments overrule arguments from the set-file).