Mule Cloud Organization Usage Test
When you create an Anypoint Platform account, a root organization is created. An organization is an account where multiple users can share resources, including applications and environments. The level of access users have to various resources depends on their assigned roles and permissions. Resource management at an organizational level plays a major role in providing seamless application performance. Therefore, it is very important to keep a vigil on the resource usage at an organizational level. Mule Cloud Organization Usage Test helps you in this regard!
This test monitors the target Mule Cloud and reports the resource usage such as the vCores consumed on different environments, applications in use, connectors in use, network connections, load balancers and load balancer workers in use, etc. This way, the test can provide a deep insight into the resource usage of the mule organization and forewarn administrators on any bottleneck conditions before it leads to any catastrophic outcomes.
Target of the test : A Mule ESB Cloud
Agent deploying the test : A remote agent
Outputs of the test : One set of results for the target Mule ESB Cloud being monitored.
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 |
---|---|---|---|
Production vCores consumed |
Indicates the number of vCores consumed on the organization for Production environments. |
Number |
Only running applications are taken into account for vCore processing usage. Stopped applications do not consume vCore.
|
Sandbox vCores consumed |
Indicates the number of vCores consumed on the organization for Sandbox environments. |
Number |
|
Design vCores consumed |
Indicates the number of vCores consumed on the organization for Design environments. |
Number |
|
Static IPs consumed |
Indicates the number of static IPs in use for the applications in the organization. |
Number |
By default, the number of static IP addresses allocated to your organization is equal to twice the number of production vCores in your subscription. |
Standard connectors |
Indicates the number of connectors in use within the organization. |
Number |
Anypoint Connectors are reusable extensions to Mule runtime engine (Mule) that enable you to integrate a Mule app with third-party APIs, databases, and standard integration protocols. Connectors abstract the technical details involved with connecting to a target system. |
Premium connectors |
Indicates the number of premium connectors in use within the organization. |
Number |
Premium connectors are available to licensed users only. Premium Anypoint Connectors must be licensed for each deployment environment. |
Production applications |
Indicates the total number of applications in use on the organization for Production environments. |
Number |
|
Sandbox applications |
Indicates the total number of applications in use on the organization for Sandbox environments. |
Number |
|
Design applications |
Indicates the total number of applications in use on the organization for Design environments. |
Number |
|
Production workers |
Indicates the total number of workers in use on the organization for Production environments. |
Number |
|
Sandbox workers |
Indicates the total number of workers in use on the organization for Sandbox environments. |
Number |
|
Design workers |
Indicates the total number of workers in use on the organization for Design environments. |
Number |
|
VPCs |
Indicates the number of VPCs in use on the organization. |
Number |
The Anypoint Virtual Private Cloud (VPC) offering allows you to create a virtual, private, and isolated network segment in the cloud to host your CloudHub workers. |
VPNs |
Indicates the number of VPNs in use on the organization. |
Number |
Anypoint VPN is used to create a secure connection between your MuleSoft Virtual Private Cloud (VPC) and your on-premises network. |
Network connections |
Indicates the number of network connection in use on the organization. |
Number |
|
Load balancers |
Indicates the number of load balancers in use on the organization. |
Number |
|
Load balancer workers |
Indicates the number of load balancer workers in use on the organization. |
Number |
Each DL(Dedicated Load Balancer) unit is equivalent of two workers handling load balancing between CloudHub workers. You can assign up to four load balancer units to a DLB. A DLB with four load balancer units assigned has eight workers. |
Deployment groups |
Indicates the number of deployment groups in use on the organization. |
Number |
|