WSO2 APIM currently supports the following alert types.
...
| Reason for triggering | If there is a sudden increase in the response time of a specific API resource. |
|---|---|
| Indication | Slow WSO2 API Manager runtime, or slow backend. |
| Description | If the response time of a particular API resource (e.g., GET /API1/1.0/user/1) of a tenant, lies outside the Xth percentile value, an alert is sent. Default percentile value is 95%. Here, it is assumed that the response time of an API resource follows a normal distribution. Percentile value gets calculated daily by default. |
Abnormal backend time
| Reason for triggering | If there is a sudden increase in the backend time corresponding to a particular API resource. |
|---|---|
| Indication | Slow backend |
| Description | An alert is sent if the backend time of a particular API resource (e.g., GET /calc/1.0/numbers) of a tenant lies outside the Xth percentile value. Default percentile value is 95%. Here, it is assumed that the corresponding backend time of an API resource follows a normal distribution. The percentile value gets calculated daily by default. |
...
| Reason for Triggering | If there is either a change in the request source IP for a specific API of an application, or if the request if from an IP used before 30 days (default). |
|---|---|
| Indication | These alerts can be considered as indications of suspicious activities carried out by a user over an API of an application. |
| Description |
The first 500 requests are used only for learning purposes by default and therefore, no alerts are sent during that time. However, the learning would continue even after the first 500 requests. This means, even if you receive continuous requests from the newly detected |
Abnormal renewal of access tokens
...
Frequent tier limit hitting (tier crossing)
...