Mule Cloud Application Usage Test

Workers are dedicated instances of Mule runtime engine that run your integration applications on CloudHub. The memory capacity and processing power of a worker depends on how you configure it at the application level. Each worker has a specific amount of capacity to process data which is denoted as vCores. Hence, before deploying a Mule application to Anypoint Runtime Fabric, determine the correct number of resources to allocate. The resources allocated to your Mule application determine the application’s performance. 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. Therefore, it is very crucial to keep a vigil on the resource allocation and usage of the applications.

This test discovers each application in the target environment and monitors the total workers allocated and remaining workers. In addition, this test also reports the worker amount and percentage of CPU usage by the application. This can help administrators to proactively determine any resource contention and promptly remediate it before the application performance is affected.

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 in the target Mule ESB Cloud being monitored.

First-Level Descriptor: Environment

Second-Level Descriptor: Application

Configurable parameters for the test

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.

Measurements made by the test

Measurement	Description	Measurement Unit	Interpretation
Total workers	Indicates the total number of workers allocated for this application on this environment.	vCores
Remaining workers	Indicates the number of workers remaining for this application.	vCores	For instance, if you have remaining workers= 2.4 and in your application you are seeing total workers = 2.6 it should be because that application is using 0.2 vCores. That means if you redeploy or stop that application you are going to have remaining workers = 2.6.
Worker amount	Indicates the amount of capacity the worker of this application have to process data or indicates the worker size.	vCores	Each worker has a specific amount of capacity to process data. This will be the worker size and it comprises of the compute, memory, and storage capacities.
CPU usage	Indicates the percentage of CPU usage by this application on this environment.	Percent
Transactions	Indicates the number of transactions available on this application in this environment.	Number	Transactions are operations in a Mule app for which the result cannot remain indeterminate. A transaction will be either complete and succeed, or it will be incomplete and fail. If a transaction fails, Mule rolls back every single operation and there will be no commit.