Common Agent Container Status Test
The main Oracle VDI Core service runs as a module within the Common Agent Container (Cacao). If you encounter any issues while working with the Oracle VDI broker, you should first check the status of Cacao as well as the status of the Oracle VDI Core service module.
This test monitors the Cacao and reports its current status.
Target of the test : An Oracle VDI Broker
Agent deploying the test : A remote agent
Outputs of the test : One set of results for the Oracle VDI broker being monitored.
Parameter | Description |
---|---|
Test period |
How often should the test be executed |
Host |
The host for which the test is to be configured. |
Port |
The port number at which the specified Host listens to. |
SudoPath |
This test executes certain privileged VDA (Virtual Desktop Access) commands to pull out the desired metrics from the broker. To enable the test to run these commands, you first need to install a sudo package on the broker host. The procedure for installing this package is detailed in Pre-requisites for Monitoring the Oracle VDI Broker in an Agent-based Manner. Once the package is installed, you need to specify the full path to the install directory of the sudo package in the SudoPath text box. |
Detailed Diagnosis |
To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
|
Measurement | Description | Measurement Unit | Interpretation | ||||||
---|---|---|---|---|---|---|---|---|---|
Agent status |
Indicates whether the Cacao is currently running or not. |
|
If the Cacao is running, then, then this measure will report the value Operational. If the Cacao is not running, then this measure will report the value Not Operational. The table below lists the numeric values that correspond to each of the states mentioned above:
Note: Typically, this measure will report the States indicated in the table above as its values. However, in the graph of this measure, the operational state of the Cacao will be represented using the numeric equivalents only - i.e., 0 and 100. |
||||||
Number of processes |
Indicates the number of processes currently running for the Cacao.
|
Number |
To know which processes are currently running for the cacao, use the detailed diagnosis of this measure. |
||||||
Memory utilization |
Indicates the percentage of memory utilized by the Cacao. |
Percent |
Ideally, the value of this measure should be low. A very high value indicates that too much memory is being consumed by the Cacao processes. |
||||||
CPU utilization |
Indicates the percentage of CPU consumed by the Cacao. |
Percent |
Ideally, the value of this measure should be low. A very high value indicates that too much CPU is being consumed by the Cacao processes. |