1 Title: Reworked configuration of process monitoring
9 The configuration of the monitoring of processes has been reworked. This was
10 mainly to overcome a bug: when the process check was used on a cluster then
11 the check parameters would be taken randomly from one of the nodes.
13 The new process monitoring works like this:
16 Statically configured checks are like before. They are configured via the ruleset
17 <i>State and count of processes</i>.
20 H2:Checks created by service discovery
22 The ruleset <i>Process Inventory</i> now does not set parameters (levels)
23 for the created services anymore. Only the settings for matching process
24 names and user remain - and of course the service description.
26 The new ruleset <i>State and count of processes</i> in the section
27 <i>Parameters for inventorized checks</i> (please do not mix up with static
28 checks here) is used for defining levels for the count, CPU usage, averaging
29 and all of the other parameters. The default is to make the check OK if at
30 least one process is being found. So from now on if you are using process
31 inventory with custom levels, you need to make configurations in <i>both
34 On the other hand that can make things easier for you. You might have a lot
35 of rulesets for detecting various processes but then only need a few rules
36 for setting levels for these services.
38 In order to make the migration easier services that have already been created
39 with previous versions of Check_MK will remain to work as they did. But
40 after a new service discovery the levels will vanish and then you have to
41 configure them in the new extra ruleset.
43 Please note: the ruleset <i>State and count of processes</i> does contain the
44 settings for matching the process and the user even when used for discovered
45 checks. The reason is that it is the same ruleset as for manual checks.
46 Setting these parameters do not make sense here in most cases. Simply leave
50 H2:Performance data - ps versus ps.perf
51 The check <tt>ps.perf</tt> is now deprecated. The normal <tt>ps</tt> check now
52 does <i>always</i> create performance data. For compatibility reasons the old
53 <tt>ps.perf</tt> is still defined but does exactly the same as <tt>ps</tt>