There are two different types of monitoring provided by ZENworks Orchestrator with the VM Management functionality: direct monitoring in the VM Management interface, and monitoring in the Orchestrator Server. The monitored data in the VM Management interface can be used to influence decisions about machines to constrain to use specific joblets and be hosts to specific VMs. For the monitored data on the Orchestrator Server, you can view the information by looking at the Jobs section of the Orchestrator Console. This information is used as feedback for jobs being executed by the Orchestrator Server.
When you are in the VM Management interface, you can access information about your grid environment. To see the monitoring perspective:
Launch the VM Management interface console (see Section 2.1.2, Launching the VM Management Interface for more information).
Clickbutton on the upper right side of the interface.
Open the Grid-Node folder in the Monitored Servers view.
Provide your login name and password.
Select the node you want to get information about.
Double-click the node icon to display a graphical edit view on the right:
Click in thefield to change the time-frame for observing the server performance.
Clickif you want to see the information in a text-based layout instead of a graphical layout.
The Orchestrator Server monitors each job it deploys. It does this through multiple means, including the Orchestrator Agent installed on each of the nodes in the data center. The Agent reports processor load, memory usage, and basic operating system and processor information. This data is constantly used by the Orchestrator Server in making decisions about where to deploy joblets for a running job. The Orchestrator Server also sends out “discovery jobs” periodically (such as when an agent on a managed resource starts) to assess capabilities of the machine to run a joblet. ZENworks Orchestrator keeps a state or model of the VM location, basic health, and action facts. These facts and information are used to monitor the progress of a joblet and can be used to automatically reassign joblets based on policies, node failure, or operator intervention. For more information about the actual monitoring elements of the Orchestrator Server, see Novell ZENworks Orchestrator 1.2 Installation and Getting Started Guide.