Skip to content

The Monitor GUI Application

Overview

An application giving graphical representation of the Agents and their workloads within the Cluster.

It is intended to provide an insight for Developers to the current workload of the Turbo Build Cluster and the progress of their own build(s).

It communicates, via network socket, with the Scheduler to obtain status information for each of the Agents in the cluster.

The Installer will create a Windows Start Menu shortcut called Turbo Monitor. The file name is bin\turbo-monitor.exe.

Below is a screenshot of the Turbo Monitor application showing a build in-progress for a Turbo Build Cluster running on AWS EC2 machines. We can see the central Scheduler (in grey) and the attached Agent machines. The dark-green Agent 'EC2AMAZ-2QJLA9J' has initiated a build and it is delegating Build Jobs (c++ compilations) to the other Agents. Each build job is a dark-green pulse around the Agent bubbles. The preparation phase for build jobs are shown as white pulses.

Turbo Build Monitor showing a build in-progress
The Turbo Build Monitor showing a build in-progress

Configuration

The primary configuration settings can be viewed and edited from The Turbo Monitor GUI application.

Right-click within the application window (or on its Windows System Tray icon) for a popup menu. Select the Settings menu item.

Turbo Build Monitor Settings
The Turbo Build Monitor Settings window

Also see the config\turbo-monitor.xml file.

For more details on the configuration files see Configuration for more details.

Operations

Right-click within the application window (or on its Windows System Tray icon) for a popup menu. Select the Cache menu item.

The following Operations are possible from this menu item :

  • Purge Cache on this Agent to Max Disk Space
  • Purge all Cache on this Agent
  • Purge all Cache on all Agents [restricted to Scheduler machine only]

These operations assist in managing the Cache (of compiled c++ object files).

Note that the Purge all Cache on all Agents menu item is quite powerful and is therefore restricted to the Scheduler machine only. Windows user login to this machine provides the security measure to ensure only the Administrator(s) of the Turbo Build Cluster can access this operation.