Microgateway 10.5 | webMethods Microgateway Help | Policies | Traffic Monitoring | Monitor Service Performance
 
Monitor Service Performance
This policy is similar to the Monitor Service Level Agreement policy and does monitor the same set of run-time performance conditions for an API in a Microgateway instance, and sends alerts when the performance conditions are violated. However, this policy monitors run-time performance at the API level. Parameters like success count, fault count, and total request count are immediate monitoring parameters and the evaluation happens immediately after the limit is breached. The rest of the parameters are Aggregated monitoring parameters whose evaluation happens once the configured interval is over. If there is a breach in any of the parameters, an event notification ( Monitor event) is sent to the configured destination. In a single policy, multiple action configurations behave as AND condition. The OR condition can be achieved by configuring multiple policies.
This policy only monitors run-time performance conditions within a single Microgateway instance. That is, the policy is not applicable across Microgateway instances holding the same APIs.
The table lists the properties that you can specify for this policy:
Parameter
Value
Action Configuration. Specifies the type of action to be configured.
Name
Specifies the name of the metric to be monitored.
You can have one of the available metrics:
*Availability. Indicates whether the API is available to the specified clients in the current interval.
*Average Response Time. Indicates the average time taken by the API to complete all invocations in the current interval. The average is calculated from the instant the API activation takes place for the configured interval.
For example, if you set an alert for Average response time greater than 30 ms with an interval of 1 minute then on API activation, the monitoring interval starts and the average of the response time of all runtime invocations for this API in 1 minute is calculated. If this is greater than 30 ms, then a monitor event is generated. If this is configured under Monitor service performance, then all the runtime invokes are taken into account.
*Fault Count. Indicates the number of faults returned in the current interval.
*Maximum Response Time. Indicates the maximum time to respond to a request in the current interval.
*Minimum Response Time. Indicates the minimum time to respond to a request in the current interval.
*Success Count. Indicates the number of successful requests in the current interval.
*Total Request Count. Indicates the total number of requests (successful and unsuccessful) in the current interval.
Operator
Specifies the operator applicable to the metric selected.
You can have one of the available operator: Greater Than, Less Than, Equals To.
Value
Specifies the alert value for which the monitoring is applied.
Destination
Specifies the destination where the alert is to be logged.
You can have the required options:
*API Gateway
*Elasticsearch
Microgateway does not support destinations other than the ones listed above.
Alert Interval
Specifies the time period in which to monitor performance before sending an alert if a condition is violated.
The timer starts once the API is activated and resets after the configured time interval. If an API is deactivated the interval gets reset and on API activation it starts afresh.
Unit
Specifies the unit for the time interval in minutes, hours, days, or weeks for the alert interval.
Alert Frequency
Specifies how frequently to issue alerts for the counter-based metrics (Total Request Count, Success Count, Fault Count).
You can have one of the following options:
*Only Once. Triggers an alert only the first time one of the specified conditions is violated.
*Every Time. Triggers an alert every time one of the specified conditions is violated.
Alert Message
Specifies the text to be included in the alert.