...
| Name | Type | Description | ||
|---|---|---|---|---|
| About to Expire Certificates Alert | Gateway | Alert for certificates that are about to expire. The alert will check for syslog message with code 0x806000e2 that were written in the last 24 hours | ||
| Already Expired Certificates Alert | Gateway | Alert for certificates that already expired - the alert will check for syslog messages with code 0x806000e1 that were written in the last 24 hours | ||
| API Error Message Count Alert | API-C | Alert when more than X (defaults to 10) API transactions ended with a specific error message, the searched message can be changed via the alert parameters, it's okay to use only a substring of the message. | ||
| API Latency Above 100ms Alert | API-C | Alert if more than 5 API Connect API calls finished with latency of over 100ms Change 5 to any other number using the field "Error Threshold" To change "100" to any other latency, you will need to edit the JSON - duplicate the alert first, as system predefined alerts' JSON cannot be edited | ||
| APIs That Ended in Error Code Range | API-C | Alert on any API transaction that ended with status code 500. You may change the range of the status code by editing the parameters JSON (for example, alert on statusCode between 300 and 600) | ||
| Domain Restarts Alert | Gateway | Alert on domain restarts | ||
| Message Codes Frequency Alert | Gateway | Alert when message codes frequency exceeds threshold value | ||
| Number of Probes Alert | Gateway | Alert if more than 1000 transactions with probles were run in the last 10 minutes | ||
| Objects Down Alert | Gateway | Alert on all the DataPower objects that are enabled in configuration but in a down state (similar to the data shown in the Failed Objects page) | ||
| Syslog Errors MessageCode Alert | Gateway | Alert when a specific syslog message is written (only messages with severity = error) | ||
| Transaction Errors Alert | Gateway | Alert when 5 or more transactions with errors ran in the last 30 minutes Please note: When duplicating this alert - the new alert name must start with "Transaction_Errors" (e.g. "Transaction_Errors_2") | ||
| API Latency Above 100ms Alert | API-C | Alert if more than 5 API Connect API calls finished with latency of over 100ms Change 5 to any other number using the field "Error Threshold" To change "100" to any other latency, you will need to edit the JSON - duplicate the alert first, as system predefined alerts' JSON cannot be edited | ||
| APIs That Ended in Error Code Range | API-C | Alert on any API transaction that ended with status code 500. You may change the range of the status code by editing the parameters JSON (for example, alert on statusCode between 300 and 600)Trans. Over 30 Secs by Service Name Alert | Gateway | Alert when more than X (defaults to 10) successful transactions took more than 30 seconds to finish (the number of seconds can be changed via the alert parameters) |
| Unused Services | Gateway | Alert when service total transactions equals to zero |
System Health Metrics
See System Health for more detailes
...