Job server rate computation

The Job server is a probe running on the execution server. It will measure some features of the execution server:

• the free disk space in kilobytes
• the free physical memory in bytes
• the free swap memory in bytes
• the idle CPU usage as a percentage between 0.0 and 1.0
• the nice CPU usage as a percentage between 0.0 and 1.0
• the total CPU usage as a percentage between 0.0 and 1.0
• the minimum required number of CPUs

This information is sent to Talend Administration Center which then computes a rate value for this server.

Some features are more important than the other. You can weight these features in the monitoring_client.properties file.

Let's call weight{i} the weight of the ith feature.

You can choose the range in which the feature is supposed to be good enough. This means you set some limits to be fulfilled by the feature of the server. For instance, a server is not a good server for the execution of the Job if it does not have 1Go of disk space. The lower limit on the disk would therefore be 1Go (to be set in the monitoring_client.properties file). Let's call Min{i} the lower limit defined on feature i and Max{i} its upper limit.

The server has an actual value for each feature. For instance, the server i has only 500 MB of free disk space. Let's call this value the actual value of the feature: value{i}.

The basic assumption is that the server is perfect as long as all of its features have actual values in the range defined by the limits. When some of its features have values outside the defined ranges, the server is not very good.