...
| 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 | This alert gets triggered if the response time of a particular API is higher than the predefined configured value. These alerts could be treated as an indication of a slow WSO2 API Manager runtime or a slow backend. |
...
| Reason for triggering | If there is a sudden increase in the backend time corresponding to a particular API resource. |
|---|---|
| Indication | Slow backend |
| Description | This alert gets triggered if the backend time corresponding to a particular API is higher than the predefined configured value. These alerts could be treated as an indication of a slow backend. If the backend time of a particular API of a tenant lies outside the predefined value, an alert will be sent out. |
Abnormal request counts
| Reason for triggering | If there is a sudden spike or a drop in the request count within a period of one minute by default for a particular API resource. |
|---|---|
| Indication | These alerts could be treated as an indication of a possible high traffic, suspicious activity, possible malfunction of the client application, etc. |
| Description | This alert is triggered if there is a sudden spike in the request count within a period of one minute by default for a particular API for an application. These alerts could be treated as an indication of a possible high traffic, suspicious activity, possible malfunction of the client application, etc. |
...
| Reason for Triggering | The response time of an API is greater than the predefined configured value specified for the same. This should occur continuously for a specified number of times (5 times by default). |
|---|---|
| Indication | The response time is too high. |
...