Microservices Runtime Components Test
The health of the components in webMethods Microservices Runtime server should be monitored for ensuring system reliability, early detection of failures, and maintaining optimal performance across integrated services. When the health of those components in webMethods Microservices Runtime server is Down, the server is unable to guarantee reliable delivery or processing of requests, and orchestrators or monitoring systems may interpret this status as a need for intervention—such as restarting or rescheduling services. This test helps the administrators to detect, respond, and prevent failures, enhancing both efficiency and reliability in managing webMethods Microservices Runtime.
Target of the test : webMethods Microservices Runtime
Agent deploying the test : A remote agent
Outputs of the test : One set of results for each component in the target webMethods Microservices Runtime server.
| 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 Administrator 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. |
|
DD Frequency |
Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 3:1. This indicates that, by default, detailed measures will be generated every third time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency. |
|
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 | ||||||
|---|---|---|---|---|---|---|---|---|---|
|
State |
Indicates the health status of this component in the target server. |
|
The values that this measure can report and their corresponding numeric values are discussed in the table below:
Note: By default, this measure reports the Measure Values discussed above to indicate the running status of the component in the target server. In the graph of this measure however, states are represented using the numeric equivalents only. The detailed diagnosis of this measure lists the details of the microservices runtime components that are in Down state and the reasons for why the components are down. |
||||||
|
Overall state |
Indicates the overall health status of this component in the target server. |
|
The values that this measure can report and their corresponding numeric values are discussed in the table below:
Note: By default, this measure reports the Measure Values discussed above to indicate the overall health status of the component in the target server. In the graph of this measure however, states are represented using the numeric equivalents only. |