Microservices Runtime Requests Test
In webMethods Microservices Runtime, an API catalogue is a centralized repository or registry that lists, organizes, and manages all available APIs and microservices within the environment. This enables discovery, reuse, and lifecycle management of APIs, making it easier for developers and consumers to find, understand, and use the right services. A service in webMethods Microservices Runtime refers to a specific business function or operation that is exposed as part of a microservice or API. Services can be implemented as REST endpoints, messaging handlers, or integration flows, and are grouped within packages for deployment and management.
Requests in webMethods Microservices Runtime are routed through the API catalogue to the appropriate service, leveraging the catalogue for discovery, access control, and management, while the service itself executes the business logic and returns the response. This test helps the administrators to monitor the request rate closely since high failed request rate can degrade service health, trigger cascading failures, hinder effective scaling, and increase operational costs, making it crucial to monitor, diagnose, and resolve the root causes promptly.
Target of the test : webMethods Microservices Runtime
Agent deploying the test : A remote agent
Outputs of the test : One set of results for each API catalogue:service 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 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. |
| Measurement | Description | Measurement Unit | Interpretation |
|---|---|---|---|
|
Total requests since the last polling interval |
Indicates the total number of requests processed by this service since the last polling interval. |
Number |
|
|
Total requests rate |
Indicates the rate at which the total requests are processed in this service. |
Requests/minute |
|
|
Successful requests |
Indicates the number of successful requests in this service. |
Number |
|
|
Failure requests |
Indicates the number of failed requests in this service. |
Number |
|
|
Other requests |
Indicates the number of other requests in this service. |
Number |
Unlike traditional synchronous incoming service calls (e.g., REST or SOAP API calls), other request types enable asynchronous, reactive, or time-driven processing patterns, which are essential for scalable and flexible microservice architectures in webMethods Microservices Runtime. |
|
Average request time since the last polling interval |
Indicates the average request time since the last polling interval. |
Milliseconds |
|