The configuration of the monitoring of processes has been reworked. This wasmainly to overcome a bug: when the process check was used on a cluster thenthe check parameters would be taken randomly from one of the nodes.
Checks created by service discovery
The ruleset Process Inventory now does not set parameters (levels)for the created services anymore. Only the settings for matching processnames and user remain - and of course the service description.
The new ruleset State and count of processes in the sectionParameters for inventorized checks (please do not mix up with staticchecks here) is used for defining levels for the count, CPU usage, averagingand all of the other parameters. The default is to make the check OK if atleast one process is being found. So from now on if you are using processinventory with custom levels, you need to make configurations in bothrulesets.
On the other hand that can make things easier for you. You might have a lotof rulesets for detecting various processes but then only need a few rulesfor setting levels for these services.
In order to make the migration easier services that have already been createdwith previous versions of Check_MK will remain to work as they did. Butafter a new service discovery the levels will vanish and then you have toconfigure them in the new extra ruleset.
Please note: the ruleset State and count of processes does contain thesettings for matching the process and the user even when used for discoveredchecks. The reason is that it is the same ruleset as for manual checks.Setting these parameters do not make sense here in most cases. Simply leavethem unchecked.
Performance data - ps versus ps.perf
The check ps.perf is now deprecated. The normal ps check nowdoes always create performance data. For compatibility reasons the oldps.perf is still defined but does exactly the same as ps