Mule Cloud Application Worker Workload Test
When a worker is impaired by hardware or software failures, including network unavailability, memory issues, server hardware failures, or file corruption, CloudHub automatically attempts to restart the application on a new worker. This can affect the performance by causing delay between the time the new worker starts and when it starts sharing the load. This is why, the load on the worker must be continuously monitored and administrators must be promptly alerted on any bottleneck conditions.
This test discovers each worker running every application on the target environment and reports the CPU utilization and memory usage to indicate its current load. In addition, this test also reports the amount of data read and written to the disk and the amount of network data in and out. These metrics helps you to identify how well the worker handles load and proactively identify any bottleneck conditions.
Target of the test : A Mule ESB Cloud
Agent deploying the test : A remote agent
Outputs of the test : One set of results for each environment:application:worker in the target Mule ESB Cloud being monitored.
First-Level Descriptor: Environment
Second-Level Descriptor: Application
Third-Level Descriptor: Worker
| Parameter | Description |
|---|---|
|
Test period |
How often should the test be executed |
|
Host |
The IP address of the host for which this test is to be configured. |
|
Port |
The port number at which the specified host listens. |
|
Username and Password |
By default, the eG agent uses the Cloudhub API version 2 (v2) to collect the metrics from the target Mule ESB Cloud or Cloudhub. To be able to connect to the Cloudhub API v2, the eG agent should be configured with the username and password of a user who is vested with the read only rights. Specify the user and password in the Username and password text boxes. |
|
Confirm Password |
Confirm the password by retyping it here. |
|
Organization Name |
To enable the eG agent to monitor a particular organization on Anypoint platform account, specify the name of that organization against this parameter. For instance, org. Doing so will enable the eG agent to monitor each of the components within the specified organization. |
|
Exclude Environments |
Here, you can provide a comma-separated list of environments that you do not want to monitor. For instance,Sandbox,Design,Production,.... By default this is set as none, indicating that this test will report metrics for all the environments on the target Anypoint platform. |
|
Exclude Applications |
Here, you can provide a comma-separated list of applications that you do not want to monitor. For instance,Helloworld,AppName,.... By default this is set as none, indicating that this test will report metrics for all the applications on the target Anypoint platform. |
|
Session Timeout |
Indicate the duration (in minutes) for which this test should wait for a response from the Anypoint Platform. By default, this is set to 60 minutes. This means that any user session that has remained inactive for more than 60 minutes will be automatically logged out from Anypoint platform. You can provide a duration between 15 minutes and 180 minutes in this text box. |
| Measurement | Description | Measurement Unit | Interpretation |
|---|---|---|---|
|
Average CPU used |
Indicates the average percentage of CPU used by this worker of this application. |
Percent |
A value close to 100% is a cause of concern, as it could indicate excessive usage. Sometimes, resource intensive applications might require additional CPU capacity. This can create CPU contention between other applications which can in turn lead to deployment failures or performance issues. |
|
Average memory usage |
Indicates the average percentage of memory usage by this worker of this application. |
Percent |
A value close to 100% indicates a bottleneck condition. |
|
Average memory used |
Indicates the amount of memory used by this worker of this application. |
KB |
|
|
Average network data in |
Indicates the amount of network data received by this worker of this application. |
KB |
|
|
Average network data out |
Indicates the amount of network data transmitted by this worker of this application. |
KB |
|
|
Average disk data read |
Indicates the amount of data read from the disk of this worker. |
KB |
Ideally, the value of these measures should be high. A consistent decrease in their value is an indication of a processing bottleneck. |
|
Average disk data written |
Indicates the amount of data written to the disk of this worker. |
KB |
