...
active tasks: the number of tasks that have been dispatched to blades and are currently running.
total slots: the sum of "slot" counts reported by all blades on the farm. Slots are an abstract unit of assignable capacity. Some sites will configure one slot per host, some will use one slot per core, others will add their own plug-ins to the blade to generate dynamic slot values.
active slots: the number of slots consumed by actively running tasks. The number used by each command is specified in the job script, and may be a dynamic number between the given "at-least" and "at-most" values.
requests / sec: an estimate of the total number of HTTP requests received by tractor-engine per second. This includes all requests from blades, browsers, and external scripts.
dispatches / sec: the rate of successful task assignments. This is the number of blade requests for work that are successfully matched with waiting tasks from the job queue, and delivered back to the blade for execution, per second.
intake backlog: an internal measure of the inbound HTTP requests to tractor-engine that have been received but not yet delegated to a specific engine subsystem for processing.
...
monitor backlog: a count of the UI-specific HTTP requests that are waiting for processing.
engine load: the normalized current "load average" on the tractor-engine host itself. The displayed value is the system one-minute loadavg, such as given by 'uptime' or 'top', but then normalized by the number of CPU cores on the host. Thus a 16-core host with 8 fully utilized cores would report a nominal loadavg of "8.0", whereas this graph will report "0.5". The intent is to indicate the overall fraction of the host's CPU capacity that is in use. This load may not always be due to entirely tractor-engine activity. Other activity on the host, such as file-serving or other running applications will also contribute to its load.
user connections: the number of recently connected client sessions. This includes Dashboard sessions as well as other clients that are also using the HTTP request protocol to receive job status updates or to request job or blade details. Since the "end" of an ongoing HTTP "session" can be difficult to characterize, the engine considers a connection to still be "current" until a relatively long interval expires without additional activity from the expected client. Specifically, fully reloading a tractor browser window temporarily cause both the old and new sessions to be counted as potentially active.