Microservices Runtime JVM Memory Test

The role of JVM memory in webMethods Microservices Runtime Server is to provide the necessary memory resources for running Java-based microservices and the runtime server processes efficiently. This test monitors every memory type on the webMethods Microservices Runtime server JVM and reports how efficiently the JVM utilizes the memory resources of each type.

Target of the test : webMethods Microservices Runtime

Agent deploying the test : A remote agent

Outputs of the test : One set of results for the target webMethods Microservices Runtime server being monitored.

Configurable parameters for the test
Parameter	Description
Test period	How often should the test be executed
Host	The IP address of the target for which the test is to be configured.
Port	The port number at which the specified target listens to. By default, this will be 5555.
User and Password	Specify the credentials of a user who has the right to execute API commands on the target and pull out metrics. The specified user is the User who should possess Administator privileges and should be associated with the Logon as a Service policy.
Confirm Password	Confirm the password by retyping it here.
SSL	Set this flag to Yes, if the target being monitored is SSL-enabled.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Total memory	Indicates the total amount of JVM memory.	MB
Committed memory	Indicates the amount of JVM memory that is guaranteed to be available for use by the memory pool.	MB	The amount of committed memory may change over time. The Java virtual machine may release memory to the system and committed memory could be less than the amount of memory initially allocated at startup. Committed will always be greater than or equal to used memory.
Free memory	Indicates the amount of memory currently available for use by the JVM.	MB
Used memory	Indicates the amount of JVM memory currently used.	MB	It includes the memory occupied by all objects, including both reachable and unreachable objects. Ideally, the value of this measure should be low. A high value or a consistent increase in the value could indicate gradual erosion of memory resources. In such a situation, you can take the help of the detailed diagnosis of this measure (if enabled), to figure out which class is using up memory excessively.
Memory usage	Indicates the percentage of used JVM memory.	Percent	Ideally, the value of this measure should be low. A very high value of this measure could indicate excessive memory consumption by the JVM, which in turn, could warrant further investigation. In such a situation, you can take the help of the detailed diagnosis of this measure (if enabled), to figure out which class is using up memory excessively.