7 This check monitors state and performance information of any linux program
8 call, for example regular running cronjobs.
10 The check uses information provided by the wrapper program {mk-job}. This
11 program is shipped with the linux agent and installed to {/usr/bin}.
12 {mk-job} is a wrapper which is called instead of the program. For
13 example, if you have a command line {nightly-backup >/dev/null} which gets
14 executed by a cronjob every night, you can change the command line to
15 {mk-job backup nightly-backup >/dev/null} to let mk-job collect information
16 about the job during runtime. In this expression, the string {backup} is
17 the identifier of the job to be executed. It must be a unique identifier
18 for this job on each host. When the job is finished, {mk-job} writes the
19 collected data to {/var/lib/check_mk_agent/job/<identifier>}. The agent sends
20 all these data to the Check_MK server.
22 The check is {CRITICAL} if the exit code of the job is not {0}, or if
23 warning or critical limits for the job age have been reached.
25 Limits can be configured with WATO.
27 This check is also cluster-aware and worst or best state is configurable.
28 Default is worst state.
31 The identifier of the job defined by the first argument to {mk-job}.
34 One check per job will be created.